Which versions of yunxohang11 are malicious?

Every published version of yunxohang11 on npm is considered malicious. Remove the package entirely.

How do I remediate yunxohang11 if I installed it?

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

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

Yes — yunxohang11 is associated with the GHSA-g83m-jwqh-vh49 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 yunxohang11 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 yunxohang11 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yunxohang11 across your stack and pipelines.

Malicious package

yunxohang11npm

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

MAL-2026-183

Immediate action

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

npm uninstall yunxohang11

What this malware does

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

fb0d6761dd8d1cd805af3477c095b5c7acdd92dd5eb9b0aa1c877e65f8ded822

0bcda0e592de29bfcadb36b9fc15f8e9286e6a900d24e8bfc6c377e6ed2c92c1

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 yunxohang11 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yunxohang11 across your stack and pipelines.
If you installed it — respond
Remove yunxohang11 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 yunxohang11 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 yunxohang11 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. yunxohang11 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-g83m-jwqh-vh49

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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