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

yzx-npmnpm

Advisory published Updated

yzx-npm is a confirmed malicious npm package (MAL-2026-18597) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yzx-npm (npm)

MAL-2026-18597
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall yzx-npm

What this malware does

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

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

b51b209fe5d701ec9bab4cc9544162b4232acfc18c867f4a1cd09ce816b1d788

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for yzx-npm (2 malicious versions).

  2. If you installed it — respond

    Remove yzx-npm 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 yzx-npm 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. yzx-npm on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2mqp-mxm3-j2fh

References

Detect & block this

O3 blocks yzx-npm-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

yzx-npm (npm) malicious package — MAL-2026-18597 | O3 Security