Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

yunxohang6npm

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

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

What this malware does

The package yunxohang6 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

1 flagged
9.9.9

Indicators of compromise (SHA-256)

3f00c325c438e731f2f5c0a66e4135cf7e682994875cdc4e2df8dbffbdb299f6
330a33730fe31c0ddee057fe9fa709d90447db3692211537a9570f70451e64a6
4931fb3daaacd47d847bc80ba906795266c4d103a73e85af3ee69e25f5be755f

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove yunxohang6 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 yunxohang6 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.

  4. How O3 protects you

    O3 blocks yunxohang6 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. yunxohang6 on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9c94-wvj8-727xRLMA-2026-01664

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks yunxohang6-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.

yunxohang6 (npm) malicious package — MAL-2026-186 | O3 Security