dejavu VS Mythic

This doesn't seem hard, you can use something like this to dwoanload the songs: https://stackoverflow.com/a/27481870/6151784 and something like this to calculate how much they match: https://github.com/worldveil/dejavu The question is would you create a (dedicated) server to do your work? Or your own pc? You could also create a very simple page where someone would paste you a YouTube profile URL and you would check all songs of this URL. Also to have a db and save information about the matching and which youtube profiles have alsready been checked. Something like that could work.

If you read the installation.md file it clearly states that it has only been tested on UNIX systems, so you might be on your own trying to get it to wor in windows.

Using neural networks seems complicated, did you tried audio fingerprinting? I have been using this audio fingerprinting library to power this anime song synchronization script. You can check Panako and dejavu too.

I want to say these few seconds match these few seconds from a different audio track. Using dejavu raw has overhead I do not need/want and hence I've been fiddling around with the fingerprint script. When modifying the global variables I can get better hits or worse hits, I will admit that even after reading there recommended article and many other sources, I can't find some good explanations about the mathematics behind the filtering after the specgram has been applied. As far as a I am aware we first apply filters to find/make fine points across the spectrogram after that we only check the distance between points along the time axis not the frequency or a hypotenuse (weird).

I used a repo called https://github.com/worldveil/dejavu to compare audio hashed fingerprints and distinguish the difference between them.

Learn the basic installation of Mythic Command and Control (C2) step by step. We'll configure Mythic C2 (open-source C2 framework https://github.com/its-a-feature/Mythic)

title: Detect Mythic Agent Traffic Over Port 8443 status: experimental author: Rotten_Sec description: Detects traffic over port 8443 that matches the WebSocket handshake used by Mythic agents to communicate with the C2 server. references: - https://github.com/its-a-feature/Mythic tags: - attack.t1071.001 - attack.t1071.004 - attack.t1071.005 - attack.t1071.006 logsource: category: network keywords: [tcp, port, 8443] condition: tcp.port == 8443 and ( "GET /websocket HTTP/1.1\r\n" in to_string($data) or "HTTP/1.1 101 Switching Protocols\r\nUpgrade: websocket\r\nConnection: Upgrade\r\n" in to_string($data) )

In my opinion, Mythic is a great choice because it is free, extremely well developed, and provides a base capability that allows you to either extend it or to leverage the work of others. With Mythic, there are currently 16 public MythicAgents and 6 different MythicC2Profiles. You can use the public agents/C2profile and then switch to internal private versions if your team decides to go that way without the need to re-learn an entire framework. It has a web front end that provides a lot of (extendable) functionality I don't see in other tools. Additionally the lead developer is always extremely eager to provide help, add features, and fix bugs. Full disclosure: I'm the primary developer of Merlin.