The Iranian espionage group Nimbus Manticore (aka Screening Serpens, UNC1549) ran phishing campaigns (T1566) against aviation and software sectors in the U.S., Europe, and Middle East, deploying MiniFast and MiniJunk V2 malware for data theft amid 2026 geopolitical tensions.
Aviation and software organizations across the U.S., Europe, and Middle East.
State-sponsored phishing and custom malware target critical sectors for espionage and data theft.
- Deliver phishing-aware training and advanced email filtering.
- Hunt for MiniFast/MiniJunk indicators and anomalous C2.
- Enforce MFA and protect credentials.
- Monitor for large outbound data transfers (DLP).
Key Technical Findings
State-sponsored phishing campaign with custom malware (Nimbus Manticore).
Aviation and software organizations.
Phishing emails with malicious links/attachments (T1566).
User interaction triggers malware execution.
Installs to survive reboots.
Attempts higher privileges.
Obfuscation techniques.
Harvests credentials for lateral movement.
Moves across the network.
Exfiltration over C2 (T1041); web-protocol C2 (T1071.001).
High – espionage and data breaches.
Technical Background
Nimbus Manticore escalated phishing (T1566) against aviation and software firms in 2026, distributing MiniFast and MiniJunk V2 via malicious emails. The chain spans execution, persistence, escalation, obfuscation-based evasion, credential access, discovery, lateral movement, collection, web-protocol C2 (T1071.001), and exfiltration over C2 (T1041).
Defenses emphasize phishing-aware training, advanced email filtering, IOC-based hunting, MFA, and DLP/egress monitoring.
Attack Chain Analysis
-
Initial Access
ActivityPhishing with malicious links/attachments (T1566).
EvidenceTargeted emails.
TelemetryEmail gateway.
Detection opportunityFilter and flag phishing.
-
Execution
ActivityRun MiniFast/MiniJunk on interaction.
EvidenceMalicious process execution.
TelemetryEDR, Sysmon EID 1.
Detection opportunityDetect malware execution.
-
Command and Control
ActivityWeb-protocol C2 (T1071.001).
EvidenceAnomalous outbound connections.
TelemetryProxy/DNS.
Detection opportunityDetect anomalous C2.
-
Exfiltration
ActivityExfiltrate over C2 (T1041).
EvidenceLarge outbound transfers.
TelemetryDLP/netflow.
Detection opportunityAlert on bulk egress.
Deep Technical Behavior Analysis
The defining behaviors are targeted phishing and custom-malware-driven espionage with covert C2/exfiltration. The strongest defenses are phishing-aware training, IOC hunting, and DLP/egress monitoring.
Specific MiniFast/MiniJunk indicators are not fully specified in the source material and require validation.
Indicators of Compromise
Indicators of Behavior
Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).
| Behavioral Indicator | Description | Data Source | Confidence |
|---|---|---|---|
| Anomalous PowerShell execution | Encoded/obfuscated commands, download cradles, or unusual parent-child process lineage. | Sysmon EID 1, PowerShell 4104 | Potential |
| Suspicious child process lineage | Office or web/service processes spawning script hosts or shells. | Sysmon EID 1, EDR | Potential |
| Security log clearing | Event log cleared or audit policy changed to hinder visibility. | Windows Security 1102, 4719 | Potential |
| New service / scheduled task creation | Unexpected persistence via services or tasks. | Security 7045, 4698; Sysmon | Potential |
| New SSH authorized_keys / cron entries | Unexpected persistence on Linux hosts. | auditd, /var/log/secure, cron logs | Potential |
| Shell history gaps or clearing | History truncated or redirected to /dev/null. | auditd, bash history | Potential |
| Web shell-like activity | New/modified server-side scripts in writable web paths; anomalous POSTs. | Web access/error logs, FIM | Potential |
| Abnormal 403/404/500 patterns | Enumeration or exploitation attempts against endpoints. | Web server logs, WAF | Potential |
| Beaconing to rare destinations | Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. | Proxy, firewall, DNS logs | Potential |
| Unusual DNS queries | High-entropy or rare domains; possible tunneling. | DNS resolver logs | Potential |
| Authentication anomalies | Spraying/stuffing, impossible travel, or MFA fatigue patterns. | IdP/VPN logs, Azure AD/Okta sign-ins | Potential |
Detection Engineering Guidance
Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.
pseudo: periodic outbound (low jitter) to newly-seen domain/IP
with small uniform payloads => alert(level=medium)
Recommended Log Sources
| Platform | Log Source | What to Look For | Priority |
|---|---|---|---|
| Windows | Security Event Log | Logon (4624/4625), service (7045), task (4698), log clear (1102) | High |
| Windows | Sysmon | Process creation (1), network (3), image load (7), LSASS access (10) | High |
| Windows | PowerShell Operational | Script block logging (4104), module logging | High |
| Endpoint | EDR / Defender telemetry | Process tree, persistence, tamper attempts | High |
| Web | Web server access logs | Anomalous POSTs, new endpoints, web-shell-like requests | High |
| Web | Web server error logs | Repeated 403/404/500 bursts on single endpoints | Medium |
| Linux | auth.log / secure | SSH logins, sudo, account changes | High |
| Linux | auditd | execve, file writes, persistence paths | High |
| Identity | IdP / VPN logs | Impossible travel, spraying, MFA fatigue | High |
| Network | DNS resolver logs | Rare/high-entropy domains, tunneling | Medium |
| Network | Proxy / firewall logs | Beaconing, direct-IP C2, exfil volume | High |
MITRE ATT&CK Mapping
| Tactic | Technique ID | Technique Name | Relevance | Detection Opportunity | Confidence |
|---|---|---|---|---|---|
| Initial Access | T1566 | Phishing | Spear-phishing emails to deliver malware. | Email gateway logs; EDR alerts on execution. | Reported |
| C2 | T1071.001 | Application Layer Protocol: Web Protocols | Misdirection of traffic for C2 communications. | Network traffic analysis; anomaly detection in outbound connections. | Reported |
| Exfiltration | T1041 | Exfiltration Over Command and Control Channel | Sensitive data exfiltration via established C2 channels. | DLP alerts; network traffic monitoring for large data transfers. | Reported |
Incident Response Guidance
- Validate exposure and confirm whether the issue applies to your environment.
- Preserve evidence (memory, disk, relevant logs) before remediation.
- Isolate affected hosts/accounts if compromise is suspected.
- Collect volatile data and review the log sources listed above.
- Hunt for the indicators of behavior and any related atomic indicators.
- Rotate potentially exposed credentials, keys, and session tokens.
- Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
- Patch affected systems; reimage where integrity cannot be assured.
- Run post-remediation validation and a BAS/security-validation retest.
Remediation and Hardening
- Patch affected systems and reduce internet-exposed services.
- Enforce MFA and least-privilege for privileged and remote access.
- Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
- Restrict script execution and constrain LOLBins where feasible.
- Monitor persistence locations and disable unnecessary services.
- Segment critical assets and review privileged accounts.
- Rotate secrets and remove credentials from configuration files.
- Tune SIEM/EDR detections, then validate controls after changes.
Business Risk
- Service disruption: degraded or unavailable systems during compromise or recovery.
- Data exposure: risk to sensitive, regulated, or customer data depending on scope.
- Regulatory exposure: potential breach-notification and compliance obligations.
- Financial impact: incident response, downtime, and potential extortion costs.
- Brand and trust impact: reputational damage with customers and partners.
- Identity blast radius: compromised accounts can expand access across cloud and SaaS.
Executive Takeaway
What leadership needs to know: State-sponsored phishing and custom malware target critical sectors for espionage and data theft. Current assessed risk: High.
Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.
Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.
Validating Your Defenses with Valitrix
The Valitrix Breach and Attack Simulation (BAS) platform empowers organizations to validate their security controls against real-world adversary techniques, including those utilized by Nimbus Manticore. By safely emulating T1566 — Phishing, T1071.001 — Application Layer Protocol: Web Protocols, and T1041 — Exfiltration Over Command and Control Channel, Valitrix allows security teams to assess how well their defenses hold up against these advanced threats. This continuous validation process ensures that organizations are not only aware of potential vulnerabilities but are also prepared to respond effectively in case of an actual attack.
This proactive approach allows teams to refine their detection capabilities and strengthen their incident response plans based on findings from simulated attacks. By iterating through this process regularly, organizations can significantly enhance their resilience against sophisticated threat actors like Nimbus Manticore.
Key Takeaways
- Nimbus Manticore is leveraging phishing campaigns with MiniFast and MiniJunk V2 malware to target critical sectors.
- The group’s activities are closely linked to geopolitical tensions, particularly in aviation and software domains.
- Phishing emails and SEO poisoning are primary distribution methods for these malware variants.
- A multi-layered defense strategy is essential for mitigating risks associated with state-sponsored cyber threats.
Frequently Asked Questions
What is Nimbus Manticore?
Nimbus Manticore is an Iranian state-sponsored hacking group recognized for conducting cyber espionage and data theft campaigns targeting critical infrastructure sectors.
How do MiniFast and MiniJunk V2 malware operate?
The malware typically executes through phishing emails that trick users into downloading malicious payloads. Once executed, these malware variants can steal sensitive data and establish command-and-control capabilities.
What are the signs of a phishing attack?
Common indicators include unexpected emails from unknown sources, poor grammar, urgent requests for information, and suspicious links or attachments.



