MediumBreach / campaignActive

Kaspersky reports AuditTeam OpsAgent ransomware posing as audit

Kaspersky says AuditTeam uses its OpsAgent framework to deploy ransomware disguised as an audit fee; check the published indicators.

Published
Exploitation
Yes, according to Kaspersky Securelist, which reports infections at dozens of organizations; no independent verification found

What happened

According to Kaspersky’s GReAT team, a group it calls AuditTeam uses a framework named OpsAgent to compromise organizations in at least seven countries and territories. Kaspersky Securelist says the campaign began in January 2026 and stayed active through October 2026 at a minimum. It lists infections in Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China, and says the group’s leak site claims victims in seven additional countries. These figures come from Kaspersky alone. The victims have not been named and the claims have not been independently verified.

Kaspersky says it found suspicious activity at an organization in Hong Kong on March 10, 2026, and that its analysis indicates OpsAgent was used by AuditTeam. It says the group’s ransom note demands an “Audit & Consulting fee”, and that paying would result in a vulnerability report being delivered instead of the stolen data being leaked. Kaspersky says the note does not mention encryption but is left by a cryptor module, so a victim who sees it already has encrypted files. Kaspersky Securelist also cites DeXpose reporting that AuditTeam claimed an attack on a Russian organization on June 25, 2026.

Technical details Kaspersky reports:

  • Capabilities: OpsAgent offers file system management, process injection, privilege escalation, keylogging, screenshot capture and network pivoting. Kaspersky says version 5.2.8 rivals Cobalt Strike in functionality.
  • Loaders: Kaspersky describes a C loader (April 2026), a .NET loader (June 2026) and a Rust loader (September 2026). The first two inject shellcode into msiexec.exe. The Rust loader runs the payload in its own process.
  • Rust rewrite: the implant moved from C++ to Rust during the campaign, adding interactive shells and WebSocket upgrades.
  • Command-and-control: domains use Amazon CloudFront subdomains, which OpsAgent can discover by reading a public GitHub repository. Kaspersky says a C2 domain for the new version was added to that repository on August 19, 2026.
  • AV/EDR killer module: installs a digitally signed Beijing Jiangmin Antivirus driver to terminate security products.
  • Cryptor module: encrypts files with AES-CBC or ChaCha20 with X25519 key exchange, and terminates database processes first.

Kaspersky also says several code patterns suggest LLM-assisted development.

Not confirmed: the initial access method, the names of victims and the volume of stolen data are not stated in the source text available to us. The Securelist article provides indicators of compromise (file hashes and file paths) that we have not reproduced.

Am I affected?

Only the indicators in the Kaspersky report can answer that, and no CVE is associated with this story in the sources. The activity Kaspersky describes was seen at organizations in the countries listed above, but the source does not say sector or size are limiting factors. Treat the following as reasons to check, not as proof of compromise:

  • Files or hosts matching the hashes or paths in the Securelist indicators section.
  • A ransom note referring to an “Audit & Consulting fee” and a vulnerability report.
  • Endpoint security products that stopped unexpectedly, or a Beijing Jiangmin Antivirus driver you did not install.
  • Unexpected access to a public GitHub repository or to Amazon CloudFront subdomains from servers where you would not expect it.

What to do now

  1. Open the Securelist report and search your EDR, file inventory and logs for the listed file hashes and file paths.
  2. Look for the Jiangmin driver being installed or loaded, and for security products terminating without an administrator action. These are the behaviors Kaspersky attributes to the AV/EDR killer module.
  3. Review process activity involving msiexec.exe and notepad.exe as injection hosts, which Kaspersky reports as defaults for some OpsAgent commands. This is our suggested hunting lead, not a Kaspersky recommendation.
  4. If you find a match or a ransom note, isolate the affected hosts and start your incident response process. Kaspersky says that when the note is visible, encryption has already happened.
  5. Check your backups and keep them offline. Kaspersky says the cryptor terminates database processes before encrypting. This step is our suggestion, not a sourced finding.

Sources