Talos details VOLTA malware’s AI-assisted victim profiling

VOLTA collects browser passwords and cookies, payment-card details, cryptocurrency seed phrases, messaging and gaming sessions, Microsoft tokens, SSH and cloud keys, Wi-Fi passwords, and screenshots.[1] Talos says the malware can use this material to build a profile that includes location, home address, employer, inferred birth year, payment-card digits and a Roblox-account valuation.[1] It also searches Gmail for purchase receipts to corroborate a home address and pulls UberEats and DoorDash order history.[1] Talos says VOLTA can run an embedded cracker against cryptocurrency-wallet vaults, rather than only copying wallet files.[1]

VOLTA sends a structured evidence bundle through OpenRouter, with instructions for the model to act as a forensic intelligence analyst.[1] The requested assessment ranks valuables by monetization tier and evaluates the victim’s security posture and password hygiene.[1] Talos characterizes the model as a triage analyst that turns stolen credentials into a prioritized dossier of the victim and monetizable assets.[1] The malware defaults to Anthropic’s Claude Opus 4.6, and its AI request uses a fixed temperature of 0.2, which Talos says is intended to make output more consistent.[1]

Talos says VOLTA can still operate without the AI step when no model key is available.[1] The AI layer therefore changes how the operator can analyze collected material, rather than being required for the malware to run.[1] Talos found six swappable configuration slots in VOLTA’s build template, filled in at build time.[1] It assessed that the malware may be sold as a builder kit, with a custom binary compiled for each buyer’s order.[1] Talos also warned that refusal resilience could become a standard feature as AI integration in malware develops.[1]

Talos found that VOLTA’s observed network endpoints were controlled by third parties and that the malware had no attacker-owned infrastructure.[1] Talos analyzed one sample and did not establish whether VOLTA had been used against real victims.[2] For organizations concerned about the browser-token collection, Talos advised restricting which processes can launch Chrome in headless mode.[2] For victims, it recommended saving the debug log, rotating exposed keys and passwords, and moving cryptocurrency stored with a plaintext seed phrase.[2] Talos says the debug log records what was collected and whether the LLM call succeeded.[1]