Which versions of yunxohang3 are malicious?

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

How do I remediate yunxohang3 if I installed it?

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

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

Yes — yunxohang3 is associated with the GHSA-8h39-jmgp-jp79 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 yunxohang3 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 yunxohang3 (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 yunxohang3 across your stack and pipelines.

Malicious package

yunxohang3npm

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

MAL-2025-192429

Immediate action

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

npm uninstall yunxohang3

What this malware does

The package yunxohang3 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.

The OpenSSF Package Analysis project identified 'yunxohang3' @ 9.9.9 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

c79fabafbf34524046a2250121c5e0713b97a9eb096f43f3aab0f6231637d012

5c2e673bf41f2c09d7193d10d854da05f9ca7460ff6ea0aa7f20c54637ec8be6

0900450d580a55eafca9c4f9d12f2d00bee5c44547a809c1bb9f919b328f6350

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 yunxohang3 (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 yunxohang3 across your stack and pipelines.
If you installed it — respond
Remove yunxohang3 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 yunxohang3 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 yunxohang3 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. yunxohang3 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-8h39-jmgp-jp79

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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