Skip to content

Add new Quark rule for Exodus malware detection - #91

Merged
haeter525 merged 1 commit into
ev-flow:masterfrom
pulorsok:rules-for-exodus
Sep 24, 2026
Merged

haeter525 merged 1 commit into
ev-flow:masterfrom
pulorsok:rules-for-exodus

Conversation

@pulorsok

Copy link
Copy Markdown
Member

Three Exodus samples — MITRE S0405 — joined the malware corpus. This adds one new rule and resyncs the retrained weights.

New rule #00279 — TelephonyManager.getDeviceId + TelephonyManager.getSubscriberId, "Collect device IMEI and subscriber IMSI identifiers".

  • Trained score +0.86
  • Fires at level 5 in 126 of 718 malware samples and 0 of 190 benign samples; benign hits never exceed level 2
  • No existing rule pairs these two APIs
  • In all three Exodus samples it fires in Llib/operatore/core/b;c, the method that registers the device with the operator's server

The rule the pruning step auto-selected (Base64.decode + KeyFactory.generatePublic) trained to -1.63 and was discarded; #00279 was chosen from the pruned candidates on its malware-to-benign separation.

Score resync — 266 existing rules changed score. No rule content changed; the diff on existing files touches only the score field.

The accompanying analysis report is submitted separately to quark-engine.

🤖 Generated with Claude Code

New rule #00279 pairs TelephonyManager.getDeviceId with getSubscriberId,
flagging code that reads the device IMEI and the subscriber IMSI in the
same method. Scores for the existing pool are resynced after retraining
against the enlarged corpus.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@haeter525
haeter525 merged commit e9ac44a into ev-flow:master Sep 24, 2026
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants