T1624.001 Broadcast ReceiversCAUTION
Open-source AI-powered offensive security harness for automated penetration testing.
Overview
Open-source AI-powered offensive security harness for automated penetration testing.
eaf7d03223fcOBSERVED · 2026-10-18What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: "T1624.001_broadcast-receivers" description: "Adversaries may establish persistence using system mechanisms that trigger execution based on specific events." category: "configuration" version: "18.1" author: "cyberstrike-official" tags: - mitre-attack - mobile - t1624.001 - persistence - android - sub-technique technique_id: "T1624.001" tactic: "persistence" all_tactics: - persistence platforms: - Android mitre_url: "https://attack.mitre.org/techniques/T1624/001" tech_stack: - android cwe_ids: - CWE-276 chains_with: - T1624 prerequisites: - T1624 severity_boost: T1624: "Chain with T1624 for deeper attack path" --- # T1624.001 Broadcast Receivers > **Sub-technique of:** T1624 ## High-Level Description Adversaries may establish persistence using system mechanisms that trigger execution based on specific events. Mobile operating systems have means to subscribe to events such as receiving an SMS message, device boot completion, or other device activities. An intent is a message passed between Android applications or system components. Applications can register to receive broadcast intents at runtime, which are system-wide intents delivered to each app when certain events happen on the device, such as network changes or the user unlocking the screen. Malicious applications can then trigger certain actions within the app based on which broadcast intent was received. In addition to Android system intents, malicious applications can register for intents broadcasted by other applications. This allows the malware to respond based on actions in other applications. This behavior typically indicates a more intimate knowledge, or potentially the targeting of specific devices, users, or applications. In Android 8 (API level 26), broadcast intent behavior was changed, limiting the implicit intents that applications can register for in the manifest. In most cases, applications that register through the manifest will no longer receive the broadcasts. Now, applications must register context-specific broadcast receivers while the user is actively using the app. ## Kill Chain Phase - Persistence (TA0028) **Platforms:** Android ## What to Check - [ ] Identify if Broadcast Receivers technique is applicable to target mobile environment - [ ] Check Android devices for indicators of Broadcast Receivers - [ ] Verify mitigations are bypassed or absent (1 known mitigations) - [ ] Assess detection coverage (1 detection strategies) ## How to Test ### Identify Attack Surface Determine if the target mobile environment is susceptible to Broadcast Receivers by examining the target platforms (Android). ### Assess Existing Defenses Review whether mitigations for T1624.001 are in place. If defenses are absent or misconfigured, this technique may be exploitable. ## Remediation Guide ### M1006 Use Recent OS Version Android 8 introduced additional limitations on the implicit intents that an application can register for. ## Detection ### Detection of Broadcast Receivers ## Risk Assessment | Finding | Severity | Impact | | ---------------------------------------- | -------- | ----------- | | Broadcast Receivers technique applicable | Low | Persistence | ## CWE Categories | CWE ID | Title | | ------- | ----------------------------- | | CWE-276 | Incorrect Default Permissions | ## References - [Android Changes to System Broadcasts](https://developer.android.com/guide/components/broadcasts#changes-system-broadcasts) - [MITRE ATT&CK Mobile - T1624.001](https://attack.mitre.org/techniques/T1624/001)
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
packages/app/public/apple-touch-icon-v3.png
packages/app/public/apple-touch-icon.png
packages/app/public/favicon-96x96-v3.png
packages/app/public/favicon-96x96.png
packages/app/public/favicon-v3.ico
Gates applied: no_behavioural_pass.
eaf7d03223fcfull audit observations/trust-audit/skill/cyberstrikeus__t1624.001_broadcast-receivers.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-18 | eaf7d03223fc | CAUTION | B | 89 | first audit |
Questions
What does the T1624.001 Broadcast Receivers skill do?
Open-source AI-powered offensive security harness for automated penetration testing.
Is T1624.001 Broadcast Receivers safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can T1624.001 Broadcast Receivers access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (eaf7d03223fc), read on 2026-10-18. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/cyberstrikeus/t1624-001-broadcast-receivers/)
Not your listing, or something out of date? Claim or update your listing.