# Veil#Drop Campaign Abuses Blogspot and PowerShell in Fileless Attacks Deploying PureLog Stealer
Securonix researchers have uncovered a sophisticated attack framework called Veil#Drop that leverages compromised websites, Google Blogspot hosting, and living-off-the-land techniques to deploy the PureLog information stealer while evading endpoint detection and response (EDR) systems. The discovery reveals a troubling trend: attackers continue to weaponize legitimate cloud services and abuse public-facing platforms to distribute malware while minimizing their operational footprint.
## The Threat: Veil#Drop Explained
Veil#Drop represents a multi-stage attack framework designed with evasion as its core principle. Rather than deploying malware directly, the framework uses a chain of obfuscated components to gradually introduce the PureLog stealer into target environments.
Key characteristics of Veil#Drop:
The framework's name—combining "veil" (concealment) with "drop" (payload delivery)—reflects its operational methodology: remaining hidden while delivering malicious code.
## Attack Chain and Technical Details
Securonix's analysis reveals a sophisticated multi-step attack progression:
### Stage 1: Initial Compromise
The attack typically begins with compromised websites that serve as distribution nodes. Attackers either gain unauthorized access to existing websites or compromise WordPress installations and similar platforms to establish command and control (C2) infrastructure that appears legitimate.
### Stage 2: Blogspot Payload Hosting
Rather than hosting malicious files on attacker-controlled infrastructure, the campaign abuses Google's Blogspot platform—a free, widely-trusted service. Blogspot's legitimate reputation makes the content less likely to be flagged by security filters and proxies.
Why Blogspot?
### Stage 3: PowerShell Execution
The actual malware deployment relies heavily on PowerShell, a native Windows management tool present on virtually all modern Windows systems. Attackers use encoded and obfuscated PowerShell commands to:
### Stage 4: PureLog Deployment
Once the environment is prepared, PureLog—an information stealer—is injected into running processes. The stealer focuses on:
## Why This Campaign Matters Now
The emergence of Veil#Drop highlights several critical concerns in the current threat landscape.
Fileless attacks remain effective: Despite years of awareness about living-off-the-land techniques, they continue to evade detection. Many organizations still rely on signature-based and file-monitoring approaches that are blind to in-memory execution. The PowerShell-centric approach leverages tools that are often whitelisted or minimally monitored in enterprise environments.
Cloud service abuse is escalating: Attackers have learned that compromising attacker infrastructure is riskier than abusing legitimate services. Google Blogspot, Microsoft OneDrive, SharePoint, and similar platforms offer attackers free infrastructure with enormous reputation advantages. Blocking these services isn't practical for most organizations, making them ideal for malware distribution.
Information stealers remain the gateway threat: PureLog and similar tools are often precursors to more serious compromise. Once credentials are stolen, attackers gain legitimate access to systems, enabling lateral movement, data exfiltration, and ransomware deployment—all while appearing as authorized users.
Supply chain compromise patterns continue: The reliance on compromised websites as distribution nodes suggests attackers are targeting content management systems and web applications with known vulnerabilities, using them as proxy infrastructure.
## Who Is Targeted?
Securonix's reporting suggests Veil#Drop campaigns are broadly opportunistic, targeting:
The campaign does not appear to be highly targeted, suggesting attackers are casting a wide net and converting credentials from high-value systems opportunistically.
## Implications for Organizations
| Risk Factor | Impact |
|------------|--------|
| Detection gaps | Fileless execution bypasses many endpoint tools |
| Credential theft | Stolen credentials enable lateral movement and authorized-looking attacks |
| Trust erosion | Legitimate services become attack vectors |
| Regulatory exposure | Data theft can trigger breach notification and compliance penalties |
| Incident response complexity | In-memory attacks leave minimal forensic evidence |
## Defensive Recommendations
Organizations should implement a layered defense:
### Detection and Monitoring
### Network Defense
### Credential Security
### Incident Response
## HackWire Analysis
Veil#Drop exemplifies a disturbing but predictable maturation in attack frameworks. Sophisticated threat actors have concluded that operational security through obfuscation and service abuse is more effective than aggressive malware distribution. By decomposing the attack across multiple legitimate platforms—a compromised website, Google Blogspot, native Windows tools, and in-memory techniques—they've created a campaign that is nearly forensically invisible.
What's particularly alarming is the *opportunistic nature* of this approach. Veil#Drop isn't a precision sniper operation; it's a broadly cast net that exploits detection blindness at scale. The framework relies on the fact that most organizations remain poor at PowerShell telemetry, credential monitoring, and behavioral analysis. For defenders, this means the threat isn't the sophistication of the payload—it's the weakness of detection at each stage.
The timeline matters too: we're seeing this technique in the wild *now*, at scale, which suggests it's proven effective. Attackers don't invest in multi-stage, evasion-first frameworks unless they're working. The shift from "build malware and host it on attacker infrastructure" to "abuse free cloud services and fileless execution" represents a meaningful evolution in attacker tradecraft.
For organizations, the implication is clear: endpoint security alone cannot stop campaigns like Veil#Drop. You need behavioral monitoring, credential protection, PowerShell visibility, and cloud security controls working in concert. The bad news is this requires more work. The good news is these capabilities are increasingly table-stakes for mature security programs.
— HackWire Editorial
## Related Coverage