Detecting Mobile Malware Behavior
Overview
Cybersecurity skill for detecting mobile malware behavior. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "detecting mobile malware behavior"
- "Analyzing suspicious mobile applications submitted by users or discovered during"
- "Monitoring enterprise mobile fleet for malicious app indicators"
- "Performing malware triage on APK/IPA samples"
Use this skill when:
- Analyzing suspicious mobile applications submitted by users or discovered during incident response
- Monitoring enterprise mobile fleet for malicious app indicators
- Performing malware triage on APK/IPA samples
- Investigating data exfiltration or unauthorized device access from mobile apps
Do not use this skill to create, enhance, or distribute malware. This skill is for defensive analysis only.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Isolated analysis environment (dedicated device or emulator, not connected to production networks)
- MobSF for automated static+dynamic analysis
- Frida/Objection for runtime behavior monitoring
- Wireshark/tcpdump for network traffic capture
- Android emulator (AVD) or Genymotion for safe execution
- VirusTotal API key for hash lookups
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Detection Scope — Identify the specific mobile malware behavior techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
- Collect Baseline Data — Gather historical logs and establish normal behavior patterns for mobile malware behavior.
- Build Detection Queries — Write detection rules, Sigma rules, or SIEM queries targeting mobile malware behavior indicators.
- Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
- Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
- Document Findings — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.
Tools
- SIEM Platform — Central log aggregation and query execution
- Sigma Rules — Vendor-agnostic detection rule format
- MITRE ATT&CK Navigator — Technique mapping and coverage analysis
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: detecting-mobile-malware-behavior3description: 'Use when detects and analyzes malicious behavior in mobile applications4 through behavioral analysis, permission abuse detection, network traffic monitoring,5 and dynamic instrumentation. Use when analyzing suspicious mobile applications for6 data exfiltration, command-and-control communication, credential stealing, SMS interception,7 or other malware indicators. Activates for requests involving mobile malware analysis,8 app behavior monitoring, trojan detection, or suspicious app investigation.910 '11domain: cybersecurity12tags:13- mobile-security14- android15- ios16- malware-analysis17- owasp-mobile18- penetration-testing19subdomain: mobile-security20author: oyi7721version: 1.0.022license: Apache-2.023nist_csf:24- PR.PS-0125- PR.AA-0526- ID.RA-0127- DE.CM-0928category: cybersecurity29metadata:30 source: https://skillmd.com/skills/oyi77/detecting-mobile-malware-behavior31---3233# Detecting Mobile Malware Behavior3435## Overview3637Cybersecurity skill for detecting mobile malware behavior. Follows industry best practices and security standards.3839## When to Use4041**Trigger phrases:**42- "detecting mobile malware behavior"43- "Analyzing suspicious mobile applications submitted by users or discovered during"44- "Monitoring enterprise mobile fleet for malicious app indicators"45- "Performing malware triage on APK/IPA samples"464748Use this skill when:49- Analyzing suspicious mobile applications submitted by users or discovered during incident response50- Monitoring enterprise mobile fleet for malicious app indicators51- Performing malware triage on APK/IPA samples52- Investigating data exfiltration or unauthorized device access from mobile apps5354**Do not use** this skill to create, enhance, or distribute malware. This skill is for defensive analysis only.555657## When NOT to Use5859- When you lack proper authorization for testing60- For production systems without change management61- When the task requires legal or compliance expertise beyond technical scope626364## Prerequisites6566- Isolated analysis environment (dedicated device or emulator, not connected to production networks)67- MobSF for automated static+dynamic analysis68- Frida/Objection for runtime behavior monitoring69- Wireshark/tcpdump for network traffic capture70- Android emulator (AVD) or Genymotion for safe execution71- VirusTotal API key for hash lookups7273## Workflow7475```python76# Example: IOC detection77import re7879IOC_PATTERNS = {80 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",81 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",82 "hash_md5": r"\b[a-f0-9]{32}\b",83 "hash_sha256": r"\b[a-f0-9]{64}\b",84}8586def extract_iocs(text: str) -> dict:87 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}88```89901. **Define Detection Scope** — Identify the specific mobile malware behavior techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.912. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for mobile malware behavior.923. **Build Detection Queries** — Write detection rules, Sigma rules, or SIEM queries targeting mobile malware behavior indicators.934. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.945. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.956. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.9697## Tools9899- **SIEM Platform** — Central log aggregation and query execution100- **Sigma Rules** — Vendor-agnostic detection rule format101- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis102103104## Process1051061. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1071. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1081. **Reporting** — Document IOCs, write findings, provide remediation recommendations109110## Verification111112- [ ] All mobile malware behavior procedures executed completely and documented113- [ ] Findings validated against multiple data sources114- [ ] False positives identified and filtered115- [ ] Results documented with evidence and timestamps116- [ ] Recommendations provided with risk-based prioritization117118## Anti-Rationalization Table119120| Rationalization | Reality |121|---|---|122| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |123| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |124| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |