Which versions of yunxohang5 are malicious?

The following npm versions of yunxohang5 are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate yunxohang5 if I installed it?

Remove yunxohang5 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 yunxohang5 — how do I know if it already compromised me?

If yunxohang5 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 yunxohang5 part of a known attack campaign?

Yes — yunxohang5 is associated with the GHSA-v4rg-gvp2-j668, RLMA-2026-01663 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 yunxohang5 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 yunxohang5 (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 yunxohang5 across your stack and pipelines.

Malicious package

yunxohang5npm

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

MAL-2026-185

Immediate action

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

npm uninstall yunxohang5

What this malware does

The package yunxohang5 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)

bef3f7dd8a9554ed61db94960f012c42f81192bb019b989608cd9db4e50dfb78

18b8411b8cd6fea01585a7c07048bb6880d2d0fe380b145a797bce43b1e96388

4a41551b23ee4b7e81c7c50fed8325716a2821bac0eb62da8f7230bad5986932

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 yunxohang5 (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 yunxohang5 across your stack and pipelines.
If you installed it — respond
Remove yunxohang5 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 yunxohang5 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 yunxohang5 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. yunxohang5 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-v4rg-gvp2-j668RLMA-2026-01663

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks yunxohang5-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