Loading malware…
Nautilus is an implant associated with espionage activity linked to Turla, although public government reporting has assessed that the tool itself was very likely Iranian in origin and later acquired and reused by Turla. It has been observed alongside the related Neuron implant and in some cases on victims that also carried Turla’s Snake malware, indicating its use within broader post-compromise intelligence-collection operations. Reported victimology has included organizations in the Middle East, particularly military establishments, government departments, scientific organizations, and universities.
Operational reporting indicates that Turla obtained not only access to Nautilus implants but also the cryptographic material and controller capabilities required to administer them legitimately, allowing the group to task existing implants and deploy them against additional victims. In some intrusions, Nautilus access appears to have been inherited from prior Iranian operations; in others, Turla reportedly used Iranian web-shell access and compromised Iranian command-and-control infrastructure to expand victim coverage and then deliver its own tooling. This places Nautilus in a campaign pattern centered on covert access, persistence, and follow-on espionage rather than disruptive effects.
Nautilus is best characterized as a backdoor-style implant used for sustained unauthorized access and post-exploitation support in targeted intrusions. Public reporting does not provide enough high-confidence technical detail in this context to enumerate a broader capability set beyond its role as an implant administered by operators during espionage operations.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
A few days later, a prolific and respected security researcher published a blog highlighting code similarities between ACIDBox and Turla Nautilus samples.
5 distinct techniques documented for this family, organized by ATT&CK tactic.
2 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Turla malware/tool referenced in advisories about the group exploiting Iranian APT infrastructure.
Turla-associated malware sample referenced only for code-similarity comparison with ACIDBox.
A Turla-associated payload cited because ACIDBOX showed code overlap with a Nautilus sample; the compared next-stage payload is decrypted and injected into a target process via reflective loading.
An Iranian-origin implant/backdoor observed on victims later accessed and used by Turla as part of intelligence collection operations.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.