Kaspersky’s latest GoSerpent research is not just another malware-family writeup. It is a reminder that modern espionage often looks less like smash-and-grab ransomware and more like quiet, patient preparation: establish access, collect the right documents, harvest credentials, build proxy paths, and come back later to move the data.

Original source: Kaspersky Securelist — GoSerpent: a persistent threat evolves with sophisticated data collection and exfiltration.

What Kaspersky reported

Kaspersky says it discovered GoSerpent-related activity in February 2026, with operations that had been underway since late 2025 against government and diplomatic entities in Southeast Asia. The broader toolchain includes the GoSerpent backdoor, a related Go-based RAT/proxy tool, credential dumping utilities, a document-collection component called ThumbcacheService, and a later exfiltration path using Stowaway with TmcLoader/TmcPayload.

The important part is the sequencing. The operators did not appear to rush straight to exfiltration. They first used access to collect sensitive files, dump credentials, and stage material. Kaspersky says the actor returned in May 2026 with evolved tooling to move previously collected data through network shares.

Why this matters beyond Southeast Asia

Bulwark Black’s read: GoSerpent is a useful model for how serious intrusions mature inside a network. The defenders’ window is not only the moment malware lands or the moment data leaves. There is a middle phase where adversaries are inventorying, collecting, staging, and validating credentials. That phase is where many small teams can still catch the intrusion if they know what to look for.

For government contractors, professional services firms, and SMBs that handle sensitive client data, this is especially relevant. You may not be a direct espionage target today, but your documents, credentials, VPN access, email history, and partner relationships can still make you valuable as a bridge into someone else’s environment.

Defensive takeaways

  • Watch for document staging, not just outbound traffic. Alert on unusual archives or database-like files appearing in shared/public user paths, especially when they contain office-document extensions or are created by unexpected services.
  • Treat credential dumping as a data-theft precursor. LSASS access, SAM hive access, Mimikatz-like behavior, and local hash dumping should trigger incident response even if no large exfiltration has been observed yet.
  • Hunt for proxy and tunneling behavior on endpoints. SOCKS5 proxying, port forwarding, reverse tunnels, unexpected listeners, and unusual outbound WebSocket/TCP patterns can indicate an actor preparing movement or exfiltration paths.
  • Baseline Windows service creation. GoSerpent-linked tooling used service-style persistence. New or renamed services running from user-writable paths deserve fast review.
  • Protect network shares like crown jewels. If an attacker can dump credentials and write to shares, staged data can move internally before it ever crosses the perimeter.
  • Use published IOCs as pivots, not as the whole detection strategy. Kaspersky published file hashes and C2 infrastructure, but the behavior chain is the more durable detection opportunity.

What to hunt this week

Security teams should look back at the last 30–90 days for unusual file collection patterns, suspicious Windows services, credential-dumping alerts that were treated as isolated events, and endpoint-to-endpoint proxy behavior. Pay attention to public user directories, deleted-document monitoring, archive creation, and abnormal access to network shares.

If you run Microsoft Defender, Sentinel, CrowdStrike, Elastic, or another EDR/SIEM stack, build one simple correlation first: new suspicious service creation plus document archive creation plus credential-access telemetry from the same host within a short window. That combination is much more meaningful than any one event by itself.

Bulwark Black assessment

GoSerpent reinforces a practical rule: data theft is a process, not a single event. The organizations that catch this kind of intrusion early are usually the ones that monitor collection and credential abuse with the same seriousness as exfiltration. For smaller teams, the goal is not perfect attribution. The goal is to detect the operational pattern before the adversary finishes the mission.