Which versions of yunxoahng2 are malicious?

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

How do I remediate yunxoahng2 if I installed it?

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

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

Yes — yunxoahng2 is associated with the GHSA-v4mq-xqfq-xcqj 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 yunxoahng2 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 yunxoahng2 (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 yunxoahng2 across your stack and pipelines.

Malicious package

yunxoahng2npm

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

MAL-2025-192428

Immediate action

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

npm uninstall yunxoahng2

What this malware does

The package yunxoahng2 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 'yunxoahng2' @ 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)

35299060aa3603ce515eb39513fdb91c14859ecb9fc41587d6b80a5b0992901c

590cb2c888056f49872da23301bfc59ab2eab0b221cd551f2074bdb586e765bc

0f8f5e6fad408a138d25de919d714b42202c0c57ad1b5d32200f17f4fe3e31af

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 yunxoahng2 (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 yunxoahng2 across your stack and pipelines.
If you installed it — respond
Remove yunxoahng2 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 yunxoahng2 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 yunxoahng2 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. yunxoahng2 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-v4mq-xqfq-xcqj

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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