{
  "family": "atom",
  "sample_count": 1,
  "category": "ransomware",
  "description": "<h3>Executive Summary</h3>\nAtom (often referencing the AtomBombing code injection technique or the Atom Ransomware variant) is a highly sophisticated malware framework designed to bypass modern security defenses. When utilizing the AtomBombing technique, it represents a \"fileless\" threat that injects malicious code without ever calling standard, heavily monitored Windows APIs, making it nearly invisible to traditional antivirus solutions.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nThe Atom malware framework is typically deployed post-compromise by advanced threat actors, or embedded within highly targeted malicious documents.\n\nIts primary characteristic is its reliance on advanced evasion:\n<ul>\n<li><strong>AtomBombing Injection:</strong> Instead of using easily monitored APIs like `WriteProcessMemory` or `CreateRemoteThread`, Atom exploits the Windows \"Atom Tables\" (a standard OS feature used to store strings and corresponding identifiers). The malware writes its malicious payload into a global atom table and then forces a legitimate process to retrieve and execute it.</li>\n<li><strong>Bypassing EDR:</strong> Because the AtomBombing technique relies entirely on legitimate OS mechanisms for inter-process communication, it effectively bypasses many Endpoint Detection and Response (EDR) solutions that rely on API hooking to detect process injection.</li>\n<li><strong>Ransomware Payload (Atom Ransomware):</strong> If the \"Atom\" identifier refers to the ransomware variant, once the injection is complete, the malware acts as a standard cryptovirus, rapidly encrypting files (often using strong AES/RSA algorithms), deleting Volume Shadow Copies, and dropping a ransom note.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThe presence of Atom (specifically the AtomBombing technique) indicates a severe breach by a sophisticated adversary. Because it is designed to evade modern security controls, a successful injection allows the attacker to execute arbitrary code, steal credentials, or deploy destructive payloads (like ransomware) with impunity.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Advanced Behavioral Analytics:</strong> Detecting AtomBombing requires EDR solutions configured to monitor for anomalous usage of global atom tables or unexpected execution flows within legitimate processes, rather than standard API monitoring.</li>\n<li><strong>Memory Forensics:</strong> Because the core payload may never touch the disk, incident responders must utilize memory forensics tools (like Volatility) to analyze the RAM of the infected machine, identify the injected code, and extract the C2 infrastructure.</li>\n<li><strong>System Re-imaging:</strong> Due to the stealthy nature of the injection, it is extremely difficult to guarantee that the system has been entirely cleaned. The most secure remediation is a complete bare-metal wipe and restoration from a trusted offline backup.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Trojan.AtomBombing",
    "Ransomware.Atom",
    "Win32/Atom"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1055",
    "T1027",
    "T1486",
    "T1490"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-01T17:18:38Z",
  "type": "Malware Framework / Ransomware",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}