Which versions of yangming708 are malicious?

The following npm versions of yangming708 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate yangming708 if I installed it?

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

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

Yes — yangming708 is associated with the GHSA-vgr6-626m-8w22, IN-MAL-2026-017531 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 yangming708 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 yangming708 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yangming708 across your stack and pipelines.

Malicious package

yangming708npm

yangming708 is a confirmed malicious npm package (MAL-2026-13845) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yangming708 (npm)

MAL-2026-13845

Immediate action

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

npm uninstall yangming708

What this malware does

The tarball contains only package.json and index.html. package.json declares main: "index.html", which is not a requirable Node module, and no preinstall/install/postinstall/prepare lifecycle scripts are declared. index.html contains an obfuscated script (wrapped in a fake Cloudflare 'Just a moment...' template) that, if opened in a browser, decodes an encoded string and calls window.location.replace to redirect to the resulting URL. Because npm install does not execute HTML and require()/import cannot load this main, installing or loading the package does not execute any code on a developer or build machine. The artifact looks like registry spam / a browser-side redirect page mispublished as an npm package, not a supply-chain attack against installers.

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

1.0.0

Indicators of compromise (SHA-256)

3c66586cb4455acd4f9845b0ac788de86f9814180ee81055925867864db2ca7f

f670e6c07175c9534c5554cc89c44a73a22d46a18a9a19140030b5b446fba17f

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 yangming708 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yangming708 across your stack and pipelines.
If you installed it — respond
Remove yangming708 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 yangming708 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 yangming708 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. yangming708 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vgr6-626m-8w22IN-MAL-2026-017531

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database