Voicemail Lures Hide JavaScript in Plain Sight
For two months, cybercriminals quietly slipped malicious files past corporate email defenses by disguising them as voicemail notifications. The twist? The attachments were SVG files — a format most scanners treat as harmless images.
Email security vendor INKY detected 26,589 malicious messages across 5,527 organizations between June 1 and August 4, 2026. The campaign ran in waves, largely pausing on weekends. The biggest spike hit on June 3, when 2,432 messages reached 1,149 companies in a single day.
And it’s still going. INKY noted the operation was active when its analysis closed.
Why SVG Attachments Slip Past Filters
SVG files are vector images, but they can also carry embedded JavaScript. That’s the core of this attack. The attachments declared a MIME type of text/plain instead of image/svg+xml, so scanners checking the stated type saw an innocuous text file rather than executable content.
Inside, a minimal graphic shell hid obfuscated script. The code reconstructed strings at runtime, fetched a remote endpoint, and used deferred execution and runtime script injection. Static analysis tools struggled to flag it because nothing looked suspicious until the browser rendered the file.
The Social Engineering Layer
The lures were personalized. In 99.5% of cases, the email subject included the local part of the recipient’s own address — making the message feel internal. Attachment names mimicked standard voicemail files, complete with XML content to reinforce the illusion.
It’s a classic pretext: a missed call, a voice message, a quick click. The recipient’s guard drops because the email looks like it came from their own company.
Internal Spoofing Carried the Campaign
The operation leaned hard on domain spoofing. INKY found that 95% of messages claimed to originate from the recipient’s own domain, yet they arrived from external senders that had never authenticated to the mail server.
That’s a red flag for trained eyes, but native filters missed it. Microsoft’s Spam Confidence Level (SCL) scoring treated 75% of the messages — 19,994 total — as harmless, assigning them an SCL of 0 or 1. Only 18% received an SCL of 5, which would typically trigger quarantine.
INKY also observed that the same template drew different native verdicts depending on the receiving mailbox. One message could be flagged in one org and waved through in another, exposing the inconsistency of default filtering.
Broad Spray, Not Precision Targeting
This wasn’t a spear-phishing operation. The median organization received just two messages, and 32% received only one. The ten most-affected companies accounted for just 6% of total volume — a clear sign of broad, untargeted delivery.
The attackers cast a wide net, betting that volume would compensate for low individual success rates. They combined several plausible signals: a familiar voicemail pretext, an image format, recipient-specific personalization, and internal sender impersonation.
The SVG attachment was the bridge. It connected social engineering to executable browser content, turning a simple click into a potential infection.
What This Means for Email Security
This campaign shows why relying solely on native spam filters is risky. Attackers are weaponizing file formats that many security stacks overlook. SVG files, in particular, are a growing vector because they’re not typically treated as executable.
Organizations should consider the following:
- Block or sandbox SVG attachments arriving via email, especially from external senders.
- Inspect MIME types rather than trusting declared headers.
- Train employees to verify voicemail notifications through official channels, not email links.
- Deploy email security tools that analyze content behavior, not just static signatures.
For more on how attackers abuse file formats, see our breakdown of phishing email evasion techniques and email spoofing prevention best practices.
The takeaway is simple: if a voicemail notification arrives as an attachment, think twice. Real voicemail systems don’t send SVG files.