Incident sheet · /security

Filed
Read
3 min · 691 words
Severity
Routine

AuditTeam's OpsAgent: Ransomware Dressed Up as a Consulting Invoice

AuditTeam's OpsAgent framework infects orgs across 14 countries, kills ~220 security processes with a signed driver, and bills ransom as an "Audit & Consulting fee" since January 2026.

The forced audit: how AuditTeam’s OpsAgent framework masks ransomware as consulting
FeedThe forced audit: how AuditTeam’s OpsAgent framework masks ransomware as consulting — geralt / pixabay

Event log

  1. Campaign ran from January 5, 2026 through at least October 2026, hitting dozens of organizations across at least seven observed countries
  2. OpsAgent v5.2.8 was rewritten from C++ to Rust and rivals Cobalt Strike in functionality
  3. AV/EDR killer module uses a signed Jiangmin antivirus driver with a ~220-process kill list
  4. C2 domains are CloudFront subdomains discovered via a public GitHub repository
  5. Ransom is framed as an "Audit & Consulting fee" paid via Tor for a vulnerability report

Since January 2026, a crew calling itself AuditTeam has infected dozens of organizations across at least seven countries — Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China — with a custom framework named OpsAgent. Their leak site claims victims in seven more, including Turkey, Japan, Spain and South Korea. The ransom note doesn't ask for a ransom at all. It demands an "Audit & Consulting fee," payable through a Tor onion address, in exchange for a vulnerability report. Pay up, and you get a remediation write-up. Refuse, and your stolen data goes public.

Researchers discovered the operation on March 10, 2026, while investigating suspicious activity at a Hong Kong organization. The payload looked like a penetration-testing utility — right down to its name. It wasn't.

How the campaign unfolded

GitHub commit history pins the start at January 5, 2026. The first victim appeared on the group's leak site on February 21. Open sources first flagged AuditTeam in March via dbdigest.com, and in June, DeXpose reported the group claiming an attack on a Russian software company.

The operators actively maintained their toolchain throughout. On August 19, 2026, a new command-and-control domain appeared in a public GitHub repository (hxxps://github[.]com/RonaldCMalcolm1983/staticPage) and was used in attacks within days. By September 29, the actor had rotated out the legacy C2 domain. OpsAgent's C2 endpoints run on AWS CloudFront subdomains — shared infrastructure that makes IP-based blocking effectively useless.

What can OpsAgent actually do?

Version 5.2.8 of the implant rivals Cobalt Strike in scope. It runs on a worker-thread architecture and supports:

  • Full file-system and process management
  • Shellcode injection, including mimikatz, pass-the-hash and .NET assembly execution via named pipes
  • Keylogging, screenshot capture and session management
  • Lateral movement through SMB, HTTP and TCP links between compromised hosts
  • A TLS-encrypted WebSocket C2 protocol with SOCKS proxying and chunked file uploads

Loaders evolved across the year: a C loader (April), a .NET loader using APC queueing (June), and by September a Rust loader that pulls an encrypted payload from C2 and runs it in-process — no remote injection needed. The implant itself was rewritten from C++ to Rust, gaining interactive shells and WebSocket upgrades along the way.

Notably, several code patterns suggest LLM-assisted development: WinAPI functions resolved by hash with plaintext names sometimes left in memory, and near-identical injection routines that differ only in arguments.

How do they kill your defenses?

A dedicated AV/EDR killer module installs a digitally signed Beijing Jiangmin Antivirus driver (kvcore.sys) that terminates security products through the \KvCorePortX0 filter port. Its kill list runs to roughly 220 entries, spanning:

  • Security products: MsMpEng, avp, ekrn, ccSvcHst
  • Monitoring: Sysmon, splunkd, wazuh-agent
  • Backups: VeeamNFSSvc, AcronisAgent, MBAMService
  • Databases: sqlservr, mysqld, mongod, redis-server
  • Even TeamViewer remote-access processes

The cryptor module then terminates SQL Server, Oracle, MySQL, PostgreSQL, MongoDB and Redis, stops Veeam, deletes shadow copies, empties the recycle bin and overwrites deleted files with random data to defeat forensics. Files are encrypted with AES-CBC or ChaCha20, each with a unique key from RtlGenRandom, exchanged via X25519 Diffie-Hellman.

Here's the trap: the note never mentions encryption — but only the cryptor drops it. If a victim is reading the note, their files are already locked.

What does this change for security teams?

Three things. First, custom multi-module frameworks were once the hallmark of APT groups with dedicated engineering budgets; AuditTeam shows a ransomware crew building comparable tooling, likely with AI assistance lowering the barrier. Second, CloudFront-based C2 means you can't rely on IP blocking — hunt for the domains and the GitHub repository instead. Third, watch for the IOCs: syscache.dat artifacts in ProgramData and user caches, kvcore.sys drivers, kv_dbg.log, and the two CloudFront domains plus 157.20.104.111 (AS 136557).

Attribution to AuditTeam carries high confidence, backed by the group's unique "Audit & Consulting fee" terminology, its Tor leak site and its remediation-report framing. The crew claims a mission to educate organizations about cybersecurity — through exploitation. For the dozens of victims across 14 countries, that education arrived encrypted.

via securelist.com (Source)

Filed under

  • ransomware
  • auditteam
  • opsagent
  • threat-intelligence
  • endpoint-security
Share this article:

More from Olivia Hart

Olivia Hart

Show full bio

News editor covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

207 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›