Daily Summary
QuasarRAT activity doubled today with 12 new samples collected against a 7-day average of 6, a 100% increase that marks the strongest single-day volume in the current tracking window. The surge is driven entirely by fresh binaries and scripts rather than any new infrastructure, with zero new C2 servers registered despite the sample spike. This pattern of rising sample volume against a flat C2 footprint is worth watching closely.
New Samples Detected
The file-type breakdown shifted notably today: 10 .exe and 2 .bat samples. While executables remain the dominant payload format, the presence of batch files in a QuasarRAT distribution chain is an outlier. QuasarRAT is typically delivered as a compiled .NET binary, so .bat files in the mix suggest either a loader or stager layer sitting in front of the final payload, or commodity infection scripts that drop the RAT via built-in Windows tooling. Security teams should treat the batch samples as likely first-stage artifacts and hunt for child-process chains spawning from cmd.exe.
7-Day Trend
Today’s count is exactly double the 7-day average, well past the 25% threshold that warrants flagging. Because new C2 servers stayed at zero, the volume increase is not coming from newly stood-up infrastructure. That points to either re-use of existing command-and-control endpoints across more victim builds, or an increase in distribution pushing the same payload family to more targets. The two .bat samples also suggest the operator (or an affiliated distributor) is varying delivery tools without changing backend infrastructure.
IOC Highlights
All 12 new IOCs are tied to today’s samples, with no corresponding C2 additions. Analysts should prioritize the hashes of the two .bat files, as script-based stagers are frequently missed by signature-first detection and often carry embedded download URLs or encoded payloads. Extracting those URLs should be the first triage step, since they may reveal the actual C2 or staging host that the binary samples connect to.
Security Analysis
The decoupling of sample volume from C2 infrastructure is the key observation. In many QuasarRAT campaigns, builders embed a static C2 address into each binary, so a doubling of samples usually brings new endpoints. Here it did not, which suggests a builder configuration reusing a small set of known hosts, common in low-sophistication commodity operations where operators rent or reuse infrastructure. Actionable recommendation: rather than chasing new hashes, pivot detection to the reused C2 hosts and network indicators, and add behavioral rules for cmd.exe and wscript.exe spawning downloads that precede .NET process injection. Blocking known QuasarRAT C2 at the perimeter will likely neutralize more of today’s samples than hash-based detection alone.