Skip to main content
Emerging ThreatsMalware & Ransomware

AuditTeam Exploits OpsAgent Framework to Disguise Ransomware Attacks

Modern office setting with cluttered desk, laptop, and blurred computer equipment in background.

"AuditTeam demands an “Audit & Consulting fee” in exchange for vulnerability reports." That phrase, lifted directly from the group's ransom note, captures both the method and the message: a ransomware campaign recast as paid security consulting.

Scope and timeline of the AuditTeam campaign

AuditTeam’s OpsAgent campaign began publicly on January 5, 2026, according to the ransom note GitHub commit history, and remained active through at least October 2026. The group’s leak site published its first listed victim on February 21, 2026. Researchers first observed suspicious OpsAgent activity targeting a Hong Kong organization on March 10, 2026, and reporting shows infections across dozens of machines in at least seven countries: China, the Philippines, Senegal, Italy, Finland, Hong Kong and Russia. The leak site additionally claims victims in Turkey, Thailand, Ukraine, Argentina, South Korea, Japan and Spain.

OpsAgent: loaders, implant architecture, and capabilities

OpsAgent is a multi-stage implant framework with functionality described as rivalling commercial tools for post-exploitation. The campaign used several loader variants over time:

  • A C loader (discovered April 2026) that injects shellcode into msiexec.exe using CreateProcessA, VirtualAllocEx, WriteProcessMemory and CreateRemoteThread.
  • A .NET loader (found June 2026) that injects via NtQueueApcThread and includes strings such as DApc, DProtect and DResume; both C and .NET loaders are obfuscated with OLLVM.
  • A Rust loader (discovered September 2026) that retrieves an encrypted payload from C2, decrypts it, parses the PE header and executes the payload inside its own process rather than injecting into another process.

The main implant (version 5.2.8) uses a worker-thread architecture with a command queue and background "jobs." It supports file system management, process control, privilege escalation, keylogging, screenshot capture, shellcode injection via named pipes, and lateral movement by linking to child agents. The C2 protocol operates over WebSocket with TLS and exchanges data in frames that also implement SOCKS proxying, chunked uploads and inter-agent forwarding.

Two specialized modules: a signed AV/EDR killer and a destructive cryptor

Two modules extend OpsAgent’s operational reach.

  • The AV/EDR killer module installs a driver presented as Beijing Jiangmin Antivirus (KV series). It communicates through a filter port named \KvCorePortX0 and responds to a 0x1D command to terminate processes. The driver carries a valid digital signature and enumerates roughly 220 targets—security products (for example, MsMpEng and ekrn), monitoring agents (Sysmon, splunkd, wazuh-agent), remote-access tools (TeamViewer_Service), backup services (VeeamNFSSvc, AcronisAgent) and database processes (sqlservr, mysqld, mongod, redis-server).
  • The cryptor module encrypts files with AES‑CBC or ChaCha20 and uses X25519 for key exchange. It generates per-file keys via RtlGenRandom and encrypts those keys with a ChaCha20 construction using a shared secret derived by Diffie-Hellman. Before encryption it actively terminates database processes (SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, Redis) and stops backup services, removes shadow copies, wipes temporary folders, overwrites deleted files with random data and then drops the ransom note. The ransom note is formatted as an audit log and offers payment via a Tor onion address in exchange for a vulnerability report—the “Audit & Consulting fee.”

AWS CloudFront C2, public GitHub discovery, and infrastructure activity

AuditTeam uses Amazon CloudFront CDN subdomains for C2 endpoints, complicating takedown and IP-based blocking because the underlying IP addresses are shared with legitimate traffic. Noted domains include d19v1tntmz2i98.cloudfront.net and d35htktbyt7nxc.cloudfront.net; a public IP observed in the campaign is 157.20.104.111. The actor maintained a public GitHub repository—hxxps://github[.]com/RonaldCMalcolm1983/staticPage—that OpsAgent can query to obtain encrypted C2 addresses. Commit history shows continuous updates through September 29, 2026, when the actor deleted a legacy C2 domain; the GitHub repository was removed in November 2026. Researchers observed a new C2 domain added to that repository on August 19, 2026 and first-seen activity for that domain on August 24 / September 6, 2026.

What this means for technologists, policymakers, and affected enterprises

  • Technologists and security teams: look for the signed Jiangmin driver artifact (kvcore.sys and kv_dbg.log paths are listed) and the process kill list that targets security, backup and database services; the Rust variant shifts C2 acquisition to AES‑GCM-protected blobs and supports WebSocket upgrades, interactive shells and numeric command identifiers.
  • Policymakers and infrastructure defenders: the use of CloudFront subdomains and a public GitHub repo highlights an operational model that blends third-party CDNs and public code hosting; the repository’s removal disrupted a discovery channel, but the presence of implants configured not to check GitHub shows removal alone did not terminate the threat.
  • Affected enterprises and procurement leaders: AuditTeam explicitly targets database processes and backup services before encryption and leaves a ransom note framed as an “Audit & Consulting fee”—organizations must treat such a note as evidence that encryption has already occurred.

AuditTeam has reframed extortion as a paid security audit, invested in a C++‑to‑Rust toolchain refresh, and combined an AV/EDR‑killing driver with a cryptor that actively disrupts backups and databases. The public GitHub repository that facilitated C2 discovery was removed in November 2026, but the campaign’s artifacts—signed drivers, CloudFront C2 subdomains, file paths and file hashes—remain concrete indicators to hunt and block.

Original analysis: The forced audit: how AuditTeam’s OpsAgent framework masks ransomware as consulting — securelist.com