Daily Summary
QuasarRAT activity rose sharply on 2026-10-25 with 25 new samples, a 257% increase over the 7-day average of 7. No new command-and-control infrastructure was registered, and no geographic targeting data was reported, so the surge appears to be a distribution-volume event rather than a new server buildout.
New Samples Detected
The file-type mix is the headline: 15 .exe samples alongside 10 script and document payloads (7 .js, 1 .xlsm, 1 .bat, 1 .vbs). Script and macro-based loaders now account for 40% of today’s volume, well above what an all-executable QuasarRAT distribution pattern would suggest. The presence of a single .xlsm and a .vbs points to at least one phishing or malspam chain using document and script execution to stage the RAT, rather than relying solely on prebuilt executables.
Distribution Methods
The blend of .js, .bat, and .vbs droppers with an Excel macro file is consistent with loader-based delivery, where a script fetches or drops the final QuasarRAT binary. The 7 .js samples in particular suggest a script-heavy campaign, likely delivered through archives or links rather than direct executable attachments. With 25 new IOCs logged but zero new C2 servers, the IOCs are most likely file hashes and loader artifacts rather than network indicators.
7-Day Trend
Today’s 25 samples are 3.5x the 7-day average of 7, a deviation well past the 25% threshold. The jump is large enough to treat as a genuine surge rather than routine variance, but it is concentrated in sample volume and loaders, not in new backend infrastructure.
Security Analysis
The absence of new C2 servers despite a 3.5x sample spike is the notable signal. In many QuasarRAT campaigns, a volume surge is paired with fresh C2 registrations as operators stand up capacity for new victims. Here, the samples appear to reuse existing infrastructure, which fits a pattern of loader repackaging: operators are churning out script variants and executables that point at known C2 endpoints to evade hash-based detection while keeping their backend stable. Security teams should prioritize detecting the .js, .vbs, and .bat loader behavior (script interpreters spawning network connections or dropping executables) over relying on updated file hashes. A practical recommendation: enable logging for wscript.exe, cscript.exe, and cmd.exe spawning child processes or outbound connections, and alert on Office applications launching script interpreters, since the single .xlsm sample indicates macro-to-script execution is in play.