NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

mayhem-wmanpm

Advisory published Updated

mayhem-wma is a confirmed malicious npm package (MAL-2025-191464) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mayhem-wma (npm)

MAL-2025-191464
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mayhem-wma

What this malware does

The package mayhem-wma was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9f00d5cfad9006d0cb83e7249554304291a746a42a2191314e1b70990e854df5
d242ed0467287371909e2fef415c86d7688c77b9a33f6b43c52d37bfc2d7fa6e

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for mayhem-wma (all published versions).

  2. If you installed it — respond

    Remove mayhem-wma 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.

  3. Did it already run?

    If mayhem-wma was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mayhem-wma on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m7f2-m25c-crj6

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mayhem-wma-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.

Explore

mayhem-wma (npm) malicious package — MAL-2025-191464 | O3 Security