Frequently Asked Questions

Product Information & Threat Research

What is LODEINFO and how does it operate in APT10 campaigns?

LODEINFO is a backdoor malware family used by APT10. After infecting a target machine, it collects and sends system information (such as current time, ANSI code page identifier, MAC address, and hostname) to its command-and-control (C2) server. LODEINFO uses a hardcoded key with the Vigenere cipher, appends random junk data to evade detection, and employs complex encryption involving SHA512 hashing and XOR operations. Later versions include locale checks (halting on 'en_US'), user agent generation, and 64-bit shellcode injection. Note: LODEINFO's techniques evolve rapidly, so organizations must continuously update their detection and validation strategies. Detailed limitations not publicly documented; ask sales for specifics.

How has LODEINFO evolved across versions?

LODEINFO has undergone several changes: v0.5.6 used two-byte XOR obfuscation for command identifiers; v0.5.9 introduced a new custom hash calculation algorithm for API resolution; v0.6.2 added locale checks and user agent generation; v0.6.3 reduced the number of backdoor commands from 21 to 11 for efficiency. Note: These changes highlight the need for continuous threat validation as attackers adapt their tools. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What features does Cymulate offer for threat validation and exposure management?

Cymulate provides continuous threat exposure management, automated exposure validation, auto-mitigation, and modules like Detection Studio and Threat Studio. These features enable organizations to validate, prioritize, and improve their cyber defenses against real threats, including advanced malware like LODEINFO. Note: Cymulate's effectiveness depends on regular updates and integration with your security stack; organizations with highly custom environments may require additional tuning. Learn more.

Which types of threats can Cymulate validate?

Cymulate can validate threats such as malware, phishing, ransomware, advanced persistent threats (APTs), insider threats, network attacks, and web application attacks. The platform is designed to simulate diverse attack scenarios, including those used by groups like APT10. Note: Cymulate's coverage is broad, but organizations with highly specialized threat models may need custom scenarios. Source.

How does Cymulate's Threat Studio help with custom attack simulations?

Cymulate Threat Studio enables teams to build and customize attack simulations to validate defenses against targeted threats. It supports the creation of custom attack chains and adapts to new threat intelligence. Note: Advanced customization may require technical expertise. Threat Studio Data Sheet.

Technical Documentation & Resources

Where can I find technical documentation on Cymulate's threat validation and detection engineering?

Cymulate provides a resource hub with industry reports, whitepapers, case studies, and technical guides. Notable resources include the Threat Studio data sheet and the Detection Engineering Automation Guide. Note: Some advanced documentation may require registration. Resource Hub

Security & Compliance

What security and compliance certifications does Cymulate hold?

Cymulate is SOC2 Type II certified and holds ISO 27001:2013, ISO 27701, ISO 27017, and CSA STAR Level 1 certifications. These attest to Cymulate's adherence to security, privacy, and cloud service standards. Note: Certification scope and coverage may vary; review official documentation for details. Security Certifications.

Use Cases & Case Studies

How has Cymulate helped organizations address advanced threats like APT10?

Cymulate enables organizations to simulate and validate defenses against advanced persistent threats (APTs) such as APT10. Case studies show measurable outcomes, such as Hertz Israel reducing cyber risk by 81% within four months and other organizations achieving faster security assessments and improved detection. Note: Results may vary based on environment and implementation. Hertz Israel Case Study.

Competition & Comparison

How does Cymulate compare to AttackIQ for exposure validation?

Cymulate offers AI-driven remediation guidance, a daily-updated attack scenario library, and an AI Copilot for automated test creation. AttackIQ focuses on continuous security validation but may not offer the same breadth of AI-driven automation or daily threat updates. Choose Cymulate for rapid, actionable validation; choose AttackIQ if you require a different integration ecosystem. Note: Cymulate's AI Copilot and daily updates are not present in all competitor offerings. Read more.

How does Cymulate differ from Mandiant Security Validation?

Cymulate emphasizes AI-powered automation, rapid deployment, and an extensive attack library with daily updates. Mandiant Security Validation is recognized for its threat intelligence and incident response heritage. Choose Cymulate for ease of use and automation; choose Mandiant if you need deep integration with Mandiant's threat intelligence services. Note: Cymulate may require additional integration for organizations already standardized on Mandiant. Read more.

Pricing & Plans

What is Cymulate's pricing model?

Cymulate uses a subscription-based pricing model tailored to each organization's needs. Pricing depends on the package, number of assets, and selected features. For a custom quote, schedule a demo with the Cymulate team. Note: Exact pricing is not publicly listed and may vary by organization size and requirements. Schedule a Demo.

Implementation & Ease of Use

How easy is it to implement Cymulate and start using it for threat validation?

Cymulate is designed for rapid, agentless deployment—no additional hardware or complex configuration required. Users can start running simulations with just a few clicks. Customer feedback highlights its intuitive interface and minimal resource requirements. Note: Organizations with highly restricted environments may need to adjust firewall or network settings. Customer Reviews.

Integrations

What integrations does Cymulate support?

Cymulate integrates with over 50 security tools, including SIEM platforms (Azure Sentinel, Splunk), EDR solutions (CrowdStrike Falcon, Carbon Black), cloud security (AWS GuardDuty), and more. This enables validation and optimization across your security stack. Note: Integration depth may vary by tool; check the full list for compatibility. Technology Alliances.

Cymulate named a Customers' Choice in 2026 Gartner® Peer Insights™
Learn More
New: Cymulate Cowork for Agentic Cyber Defense Engineering
Learn More
New Bitsight Integration: Turn Threat Intelligence into Validated Security
Learn More
Introducing Cymulate Vero AI for Agentic Cyber Defense Engineering
Learn More

APT10 - Tracking down LODEINFO

November 9, 2022

After infecting the target machine, the LODEINFO backdoor beacons out machine information to the C2, such as current time, ANSI code page (ACP) identifier, MAC address and hostname. The beacon also contains a hardcoded key (NV4HDOeOVyL) used later by the age-old Vigenere cipher. Furthermore, randomly generated junk data is appended to the end of the data, possibly to evade beaconing detection based on packet size. The encryption function used to send data was also modified, making it even more complicated. As observed in previous variants, it takes the first 48 bytes of the SHA512 hash value of the data to be sent. Then it XORs the data using a four-byte XOR key that is equal to the elapsed running time, and prepends it before the data. The first 16 bytes to be sent are from another SHA512 hash value, this time taken from the previously mentioned hardcoded AES key (NV4HDOeOVyL). It encrypts 11 bytes at the end of a base64-encoded payload (with replaced padding from "=" to ".") to dynamically generate the second Vigenere cipher key and the variable of the final generated data. The second key is used by the Vigenere cipher to encrypt the base64 encoded header (url-safe replaced padding from "=" to "."). Finally, the data to be sent to the C2 is produced using the second key, the encrypted header, and the payload through the complex steps described above. LODEINFO v0.5.6 backdoor command identifiers are obfuscated with a two-byte XOR operation. Before comparing a command identifier, an XOR operation is applied for each command. Version 0.5.9 has a new hash calculation algorithm compared to v0.5.8. The hashing algorithm is used by the malware to calculate hashes for API function names, to resolve the function addresses. In this case it seems to be a custom algorithm developed by the actor. The logic of the hash calculation has an XOR operation with a two-byte key at the end and the hardcoded XOR key, which is different in each sample. In LODEINFO v0.6.2 and later versions, the shellcode has a new feature that looks for the "en_US" locale on the victim's machine in a recursive function and halts execution if that locale is found. LODEINFO v0.6.2 is generating user agent for C2 communications and supporting the injection of the 64-bit shellcode in 'memory' command. As for updates implemented in the LODEINFO backdoor commands, the obfuscation method using two-byte XOR encryption for backdoor command identifiers as well as the debug strings remained untouched up to version 0.5.6. However, in version 0.6.3, the actor removed some of the unnecessary backdoor commands to improve the efficiency of the backdoor. The number of backdoor commands was reduced from 21 in v0.6.2 to 11 in v0.6.3.