Breakglass Intelligence reported a credential-stealing campaign delivering AgentTesla v3 through spear-phishing emails masquerading as purchase orders or request-for-quote documents. The infection chain used a heavily obfuscated JavaScript or JScript attachment that launched XOR-decrypted PowerShell, reflectively loaded a .NET component identified as DEV.dll, and performed process hollowing into aspnet_compiler.exe to run the final payload. The malware established persistence through %APPDATA%\GLOZVJ\GLOZVJ.exe, a Startup shortcut, and an HKCU\Run value named GLOZVJ, while a watchdog loop re-injected the payload if the host process was terminated.
The payload harvested credentials and data from more than 40 browsers, over 20 email clients, FTP and VPN software, Discord tokens, Windows Credential Manager, clipboard contents, screenshots, and keystrokes, then exfiltrated the data over SMTP through mail.cottondreams.org on a Ukrainian VPS at 31.222.235.198. Reports said the server used Exim, Dovecot, nginx, OpenSSH, ProFTPD, and FASTPANEL, and that plaintext SMTP credentials and weak certificate hygiene exposed poor operator security. Breakglass linked the infrastructure to activity dating back to domain registration in March 2024 and related samples seen since January 2025, assessing the operation as a persistent, financially motivated AgentTesla MaaS campaign with possible overlap with West African BEC-style tradecraft.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
On 2026-03-14, Breakglass published analysis of the five-domain PS.Maloader campaign, describing Cloudflare-shielded infrastructure, method-based content switching on portal-idos.network, exposed registrant details, and banker-style stage-2 behavior. The report assessed it as a low-detection MaaS operation likely distributed through a single phishing wave.
On 2026-03-12, Breakglass published detailed reporting on the AgentTesla v3 campaign, including persistence mechanisms, plaintext SMTP credentials, and exfiltration via mail.cottondreams.org on Ukrainian-hosted infrastructure at 31.222.235.198. The report also assessed the operation as likely tied to an AgentTesla MaaS operator or subscriber.
On 2026-03-12, Breakglass observed a fully weaponized AgentTesla v3 campaign delivered through spear-phishing emails with fake purchase order or RFQ-themed JavaScript attachments. The five-stage chain used obfuscated JavaScript, PowerShell, a reflective .NET loader, and process hollowing into aspnet_compiler.exe.
Between March 4 and March 14, 2026, a malware-as-a-service loader campaign used five newly registered domains to deliver nearly identical PowerShell stage-1 droppers. The infrastructure was fronted by Cloudflare and used rotating domains, including a typosquat of the idOS staking portal.
Breakglass reported related AgentTesla campaign samples and activity tied to the same infrastructure beginning in January 2025. This indicated the operator had been running the campaign or closely related activity for over a year.
The domain cottondreams.org, later used for SMTP exfiltration in an AgentTesla v3 campaign, was registered in March 2024. Breakglass linked this registration to a long-running financially motivated operation.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
intel.breakglass.tech
Open sourceintel.breakglass.tech
Open sourceintel.breakglass.tech
Open sourceintel.breakglass.tech
Open sourceintel.breakglass.tech
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.