Daily Summary
Agent Tesla activity reached 100 new samples on 2026-11-15, a 63% increase over the 7-day average of 61 and the highest single-day count in the current reporting window. The surge is driven almost entirely by JavaScript-based delivery, which accounts for 78 of 100 samples. No new C2 servers were registered, meaning the increase reflects higher distribution volume through existing infrastructure rather than a fresh backend build-out.
New Samples Detected
The file-type mix marks a clear shift toward script-based execution. JavaScript (.js) now represents 78% of daily volume, while compiled executables (.exe) are down to 9 samples. The remaining tail (.ps1, .bat, .lnk, .pif, .msg, .tmp, .bin) is fragmented: one or a few samples each. The single .msg sample is worth noting, since container formats like .msg are frequently used to smuggle script attachments past mail gateways that only inspect common archive types. The spread of .lnk and .pif indicates the loader chain is still relying on shortcut and legacy executable tricks as secondary paths.
Distribution Methods
The dominance of .js strongly suggests a malspam wave pushing script attachments or links to script payloads, rather than a drive-by or supply-chain vector. Agent Tesla operators have repeatedly used script loaders to fetch the final stealer from remote hosts, which keeps the delivered file small and evades signature matching. With 100 new IOCs logged and zero new C2 servers, the infrastructure is being reused at higher throughput, consistent with a broad phishing campaign riding on established hosting.
7-Day Trend
Today’s count exceeds the 7-day average by 63%, well beyond the 25% deviation threshold. The jump is volume-driven, not capability-driven: no new C2, no new file families outside the script-heavy pattern. This pattern - rising sample count against flat infrastructure - typically indicates a spam run scaling up rather than a new variant release.
Security Analysis
The key observation is the mismatch between record sample volume and zero new C2. In prior Agent Tesla waves, sample surges were often paired with fresh domains and IPs as operators rotated infrastructure. Here, volume is scaling on the same backend, which is characteristic of a high-volume spam run reusing an established panel rather than a new campaign build. That makes the loaders the more valuable detection point: the .js and .ps1 stagers are likely consistent across samples, so hunting on script-loader behaviors (WScript/CScript spawns, PowerShell download cradles, child processes from mail clients) will catch the wave even as individual payload hashes rotate. Recommended action: prioritize mail gateway rules blocking script attachments (.js, .ps1, .lnk, .pif) from external senders and alert on Office or mail client processes spawning wscript, cscript, or powershell.