Opens in a new tab

AuditTeam Ransomware Masks Extortion as Audits

AuditTeam’s OpsAgent used in multi-country ransomware-style attacks

AuditTeam ransomware disguises encryption and extortion as a professional security review. Its demand for an “Audit and Consulting fee” is delivered only after the victim’s files have already been encrypted.

Kaspersky published the first detailed technical analysis of the campaign on 18 November 2026. Its investigation found that the AuditTeam group had compromised dozens of organisations across Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China, with activity continuing through at least October 2026.

AuditTeam ransomware campaign timeline

GitHub commit history examined during the investigation indicates that the campaign began on 5 January 2026. AuditTeam’s leak site listed its first victim on 21 February, establishing that the group was publicly naming organisations within weeks of the operation starting.

On 10 March 2026, Kaspersky detected suspicious activity targeting an organisation in Hong Kong. Investigators identified OpsAgent, a post-exploitation framework designed to resemble a penetration testing utility, and subsequently connected related infections in other countries.

Data Breaches Digest publicly named “Audit Team” as a new data-leaking ransomware operator on 2 April 2026. On 25 June, AuditTeam claimed an attack against Russian software company I-SYS, a posting independently recorded by several ransomware trackers and security blogs.

The technical development of OpsAgent continued throughout the campaign. Important dates include:

  • April 2026: Investigators discovered a C-language loader that injected OpsAgent shellcode into a Windows process.
  • June 2026: A .NET loader variant was identified.
  • 19 August 2026: A new command and control domain was added to a public GitHub repository and later used in attacks.
  • September 2026: A Rust loader was discovered, reflecting the framework’s transition away from its earlier C++ implementation.
  • October 2026: AuditTeam ransomware activity remained active.
  • 18 November 2026: Kaspersky published its detailed account of the operation, including technical indicators.

How OpsAgent supports AuditTeam ransomware

OpsAgent version 5.2.8 provides operators with broad control over compromised Windows endpoints and servers. Its capabilities include file and process management, privilege escalation, keylogging, screenshot capture, shellcode injection and network pivoting between affected systems.

The framework can also create interactive command shells, establish SOCKS proxies and upload files in chunks. Custom frame types allow one compromised OpsAgent installation to forward traffic to another, while SMB-based linking helps attackers move through a victim’s internal network.

Three loader variants observed during 2026

The C loader first seen in April launches msiexec.exe and injects shellcode using standard Windows functions, including CreateProcessA, VirtualAllocEx, WriteProcessMemory and CreateRemoteThread. It uses OLLVM control-flow flattening to make analysis more difficult.

The .NET loader discovered in June uses NtQueueApcThread for injection and also targets msiexec.exe. Its embedded strings include DApc, DProtect and DResume, and it is similarly protected against straightforward analysis.

The Rust loader identified in September follows a different approach. It downloads an encrypted payload from the command and control server, decrypts it and runs its Execute export within the current process. This avoids the remote process manipulation used by the earlier loaders.

CloudFront and GitHub used for command and control

OpsAgent communicates with command and control infrastructure through WebSocket connections protected by TLS. The servers are placed behind Amazon CloudFront subdomains, which can make malicious traffic harder to distinguish from legitimate use of a widely trusted cloud service.

The implant can obtain a server address from the public GitHub repository hxxps://github[.]com/RonaldCMalcolm1983/staticPage. The configuration is base64 encoded, enclosed by the markers GetConfig and EndConfig, and encrypted with AES-CBC using a key derived from the SHA-256 value f4bb8c7e15d8b98d535eb20b09176b3d.

Commands can launch background jobs through named pipes. Additional shellcode is delivered from the server and obscured with the XOR key 604902af7b70b271. The default process used for injection is msiexec.exe, while a monitoring function uses notepad.exe.

Signed driver disables antivirus and EDR tools

A specialised OpsAgent module attempts to terminate antivirus and endpoint detection and response processes before encryption. It installs a digitally signed Beijing Jiangmin Antivirus driver and communicates through the minifilter port \KvCorePortX0.

The module sends a 0x1D command followed by the filename of a targeted security process. The driver then terminates that process. The related improper access control issue in the Jiangmin Antivirus 21 kvcore.sys driver is tracked as CVE-2026-19193, and public proof-of-concept material is available.

This is a Bring Your Own Vulnerable Driver technique. Because the driver is legitimately signed, Windows may trust it unless vulnerable driver protections, application controls or an updated driver blocklist prevent it from loading.

Encryption hidden behind a consulting demand

The AuditTeam ransomware cryptor supports AES-CBC and ChaCha20 file encryption, with X25519 used for key exchange. Before encrypting data, it terminates database processes so that active database files are unlocked and can be encrypted, increasing disruption to servers and business applications.

The resulting note does not plainly describe itself as a ransomware demand. Instead, AuditTeam requests an “Audit and Consulting fee” and promises to provide a vulnerability report if the organisation pays. It also threatens to publish stolen data if payment is not made.

However, the note is deposited by the cryptor module. Its appearance therefore means encryption has already occurred, regardless of the group’s attempt to present the payment as a consulting arrangement.

Current exploitation status and affected systems

AuditTeam ransomware has been used in confirmed, in-the-wild intrusions rather than laboratory testing. Kaspersky observed infections across seven countries through October 2026, while the group’s leak site claimed victims in additional countries.

The documented tooling targets Windows endpoints and servers. Systems hosting on-premise databases are particularly relevant because the cryptor deliberately stops database processes before encryption. Independent trackers corroborate the group’s existence and victim postings, although the OpsAgent name, Rust rewrite and CloudFront design were documented only by Kaspersky at the time of publication.

What organisations should do now

Organisations should prioritise controls that address the specific behaviour reported in this campaign:

  • Search endpoint and network telemetry for the published OpsAgent indicators, including the GitHub bootstrap path, configuration markers and unexpected CloudFront WebSocket traffic.
  • Monitor unusual use of msiexec.exe and notepad.exe, particularly where injection, named pipes or unexplained outbound connections are present.
  • Block vulnerable Jiangmin kvcore.sys drivers and keep the Microsoft vulnerable driver blocklist current through App Control for Business.
  • Enable Memory Integrity, also known as HVCI, on compatible Windows systems to strengthen protection against malicious or vulnerable drivers.
  • Investigate unexpected termination of security tools or database services as a possible precursor to encryption.

The campaign’s consulting language should not distract responders from its technical reality. Affected systems may already have experienced credential capture, lateral movement, data theft and encryption by the time the purported audit notice appears.

Originally reported by securelist.com.

Share this bulletin

About the Author

Rob McBride Headshot - CyPro Partner and leading cyber security expert

Rob McBride

Partner

  • CISSP
  • ACA Chartered Accountant
  • MPhil
  • BSc
  • SOC 2
  • ISO 27001

Rob McBride

Rob is a Founding Partner at CyPro and a highly experienced CISO. Beginning his career with a successful tenure at Deloitte, Rob has since amassed a wealth of experience, notably serving as a cyber security advisor to the UK government and spearheading cloud security transformations for several global banks.

At CyPro, Rob leads the managed service business line, working extensively across multiple sectors including telecommunications, technology, higher education, travel, and retail. He is passionate about equipping small and medium-sized businesses (SMBs) with robust cyber security strategies to fuel their growth.

View Profile
Back to Bulletins

Related CyPro Services

  • Managed Detection and Response (MDR)

    Managed Detection and Response (MDR) is an end-to-end managed service designed to help organisations detect, analyse and respond to cyber threats quickly and effectively. It...
    View Service
CyPro Cookie Consent

Hmmm cookies...

Our delicious cookies make your experience smooth and secure.

Privacy PolicyOkay, got it!

We use cookies to enhance your experience, analyse site traffic, and for marketing purposes. For more information on how we handle your personal data, please see our Privacy Policy.

Schedule a Call