Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document why malcontent is often detected as malware by other scanners #727

Open
tstromberg opened this issue Dec 18, 2024 · 0 comments
Open

Comments

@tstromberg
Copy link
Collaborator

It turns out that Elastic Security isn't alone (#78)

From https://www.virustotal.com/gui/file/b6f90aa5b9e7f3a5729a82f3ea35f96439691e150e0558c577a8541d3a187ba4/detection

  • Avast: MacOS:Joker-B [Trj]
  • AVG: MacOS:Joker-B [Trj]
  • Avira (no cloud): OSX/GM.Joker.DS
  • ClamAV: Legacy.Trojan.Agent-37025
  • Cynet: Malicious (score: 99)
  • Google: Detected
  • Kaspersky: HEUR:Trojan-PSW.OSX.Amos.n
  • MaxSecure: Trojan.Malware.121218.susgen
  • Rising: Backdoor.JokerSpy/OSX!1.E753 (CLASSIC)
  • Sangfor Engine Zero: HackTool.Win32.Template_Py_v3_3_to_v4_x.uwccg
  • SentinelOne (Static ML): Static AI - Malicious Mach-O
  • WithSecure: Malware.OSX/GM.Joker.DS

My guess is that by subtly modifying the Joker YARA rules we can cut the hit rate in half, but we should definitely document why this occurs (YARA rules often match any program that implements the same YARA rule).

@tstromberg tstromberg changed the title Add documentation to explain why malcontent is detected as malware by other scanners Document why malcontent is often detected as malware by other scanners Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant