Repository navigation
Add Quark malware analysis report for BrasDex - #986
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #986 +/- ##
=======================================
Coverage 81.28% 81.28%
=======================================
Files 84 84
Lines 7923 7923
=======================================
Hits 6440 6440
Misses 1483 1483
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
haeter525
left a comment
There was a problem hiding this comment.
Two questions about the coverage-gap notes.
1. T1516 is counted as confirmed but has no section. Please add one, and update "the 2 listed below" and "17" in the intro.
2. For T1426, T1417.002 and T1437.001: what's a per-sample check? If the rule has 100% confidence, they should appear in the behavior map.
@haeter525 Thanks for the review — all addressed in 1. T1516 section. Added a section for T1516 Input Injection (map, call walkthrough, 5 rules) and updated the intro to "3 were confirmed", "the 3 listed below" and "the other 16 techniques". 2. "Per-sample check" for T1426 / T1417.002 / T1437.001. Dropped that wording. 100% confidence alone doesn't produce a map here — the matched behavior must also pass a MITRE alignment check against the technique definition. T1426 (phone-number lookup only) and T1437.001 (generic HTTP only) failed that check, so no map was generated; they now sit under "Rules fired at full confidence, but the matched behavior did not match the technique definition". T1417.002 is a different case, see below. Additional note. While revising, I also renamed "Rule hits, but no behavior-map cluster" to "Rule hits only in third-party library code" (T1417.002 is now here) and added a note explaining why these have no map: a map is only generated when at least one matched parent method is in the app's own package; hits whose parent methods are all in library/framework code are excluded, since they reflect SDK behavior shared by any app using that library rather than family-specific behavior. The PR description is updated to match the file. |
BrasDex Malware Family Analysis Report
BrasDex is an Android banking malware reported by ThreatFabric on 2022-12-15. According to that report, it initially posed as Android settings applications while targeting Brazilian banking applications, and in its latest campaign it started posing as the Banco Santander BR banking application. The family label used here comes from the MalwareBazaar signature BrasDex, under which both analysed samples were collected. This report checks the samples against the 19 MITRE ATT&CK techniques listed for S0480 Cerberus, using Quark's existing rules. Check here for the rule set.
Quark's rule classification flagged 2 of 2 BrasDex samples as high-risk in this experiment (detection rate 100%). Benign-cohort false-positive rate was not measured here. See tested APKs below.
Identified Well-Known Threats
This section uses the technique list of the S0480 Cerberus software entry as its reference taxonomy; this does not mean BrasDex is Cerberus. Of the 19 techniques listed for S0480, 18 were mapped to at least one Quark rule and evaluated against the BrasDex samples, and 3 were confirmed by Quark behavior maps; the 3 listed below are shown as sections. See the coverage-gap notes at the end of this section for the other 16 techniques.
The behavior maps below come from two samples: the T1430 map from
3b66805144a14cb00bb58f41690e529c9e75b265faecbdb594c6c9f0f74892ed.apk(packagecom.ourselves.resort), and the T1516 and T1628.001 maps fromb14412435de7ebe13c434eef79a5c24dc2c48e5483d9db2aef30b569738f4b32.apk(packagecom.mydocs.documents). Both samples were used to compute the detection-rate figure above.Each section below corresponds to one technique from the table above. Within each section we first quote the MITRE definition, then show the Quark behavior map extracted from the representative sample's bytecode, then walk through the call sequence and list the underlying rules.
1. T1430 Location Tracking
T1430 Location Tracking — attack.mitre.org
In sample
3b66805144a14cb00bb58f41690e529c9e75b265faecbdb594c6c9f0f74892ed.apk(packagecom.ourselves.resort),LO00OOOOO/_;__calls the Android API that returns the device's last known location.Behaviors detected by Quark:
2. T1516 Input Injection
T1516 Input Injection — attack.mitre.org
In sample
b14412435de7ebe13c434eef79a5c24dc2c48e5483d9db2aef30b569738f4b32.apk(packagecom.mydocs.documents),Lcom/mydocs/documents/Services/serviceMagic;onAccessibilityEventcalls four helper methods:Lcom/mydocs/documents/b/d;a,Lcom/mydocs/documents/b/d;b,Lcom/mydocs/documents/Services/serviceMagic;aandLcom/mydocs/documents/Services/serviceMagic;b. Across these five methods, Quark matched the 5 rules listed below: they find accessibility nodes by view ID, get the root node of the active window, read a node's on-screen bounds, and perform accessibility actions on nodes. The map's call graph contains no other rule behavior.Behaviors detected by Quark:
3. T1628.001 Suppress Application Icon
T1628.001 Suppress Application Icon — attack.mitre.org
In sample
b14412435de7ebe13c434eef79a5c24dc2c48e5483d9db2aef30b569738f4b32.apk(packagecom.mydocs.documents),Lcom/mydocs/documents/b/f;hcalls the API sequence that hides the current app's launcher icon.Behaviors detected by Quark:
Coverage-gap notes
Existing rules do not detect this technique
com.mydocs.documents, but it shows UI inspection and interaction through the accessibility service, not keystroke capture.com.mydocs.documents, but it shares the T1516 call graph and shows accessibility UI interaction only, with no sign of app removal.Rule hits only in third-party library code
These hits are excluded because every matched parent method is in third-party library or framework code, not in the app's own package. Such code reflects SDK behavior shared by any app that bundles the library, so it is not counted as behavior of this family.
No related behavior detected (4) — T1582 SMS Control, T1636.003 Contact List, T1636.004 SMS Messages and T1633.001 System Checks. No related rule hit was recorded in either sample (T1633.001 has no Quark rule mapped to it), so no behavior map was formed for these techniques.
List of Tested APKs
The table below lists the APKs we tested.