Which versions of cwanner are malicious?

The following npm versions of cwanner are flagged malicious: 9.2.0. Treat any of these as compromised.

How do I remediate cwanner if I installed it?

Remove cwanner from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed cwanner — how do I know if it already compromised me?

If cwanner was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is cwanner part of a known attack campaign?

Yes — cwanner is associated with the RLMA-2025-05713, RLUA-2025-06106, RLUA-2026-01229 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cwanner across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cwanner (version 9.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cwanner across your stack and pipelines.

Malicious package

cwannernpm

Malicious code in cwanner (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191572

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cwanner

What this malware does

The package cwanner was found to contain malicious code.

Malicious versions

1 flagged

9.2.0

Indicators of compromise (SHA-256)

83cbfc5ae74da819614d4aa3c2766a9ba03677afa884d88cf430f500f6c32230

b802af5dc124ecff02d4bd0f8cb34612fa149151e1dea636d8235762f0e8c7ce

a46373bd0ee89096e161239acb1c60fa172e64df7d4e8897977bc2aa3581316e

44eb34a89a5869bd2f714348e5e484a191c56d816055b5a4b8a5b5d334e5309c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cwanner (version 9.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cwanner across your stack and pipelines.
If you installed it — respond
Remove cwanner from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cwanner was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cwanner before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cwanner on npm has been identified as a malicious package (version 9.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05713RLUA-2025-06106RLUA-2026-01229

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cwanner-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring