Which versions of yangming8 are malicious?

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

How do I remediate yangming8 if I installed it?

yangming8 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed yangming8 — how do I know if it already compromised me?

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

Yes — yangming8 is associated with the GHSA-f3hv-h6vj-6j6r, IN-MAL-2026-017533 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 yangming8 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 yangming8 (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 yangming8 across your stack and pipelines.

Malicious package

yangming8npm

yangming8 is a confirmed malicious npm package (MAL-2026-13846) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yangming8 (npm)

MAL-2026-13846

Immediate action

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

npm uninstall yangming8

What this malware does

The tarball's only shipped file is index.html, declared as the package's main. There are no lifecycle scripts, no JavaScript entry point, no dependencies, and no library surface — installing or require()-ing the package does not execute the payload on the installer's machine. The HTML presents a fake Cloudflare 'Just a moment...' verification page and, after a 1-second setTimeout, runs obfuscator.io-style JavaScript that reconstructs a destination URL from split string literals ('gin.microc' + 'loud.homes' + '/') and calls window.location.replace on it, forwarding the original query string. The destination is a lookalike domain at login.microcloud.homes (impersonating MicroCloud). The package appears to exist solely to host the phishing lander for retrieval via npm CDN mirrors (unpkg/jsdelivr), abusing the registry as static hosting for a browser-side credential-phishing page. Because the harm targets end users who load the HTML in a browser via a CDN URL — not developers who npm install this package — the installer-side risk is minimal, but the abusive distribution warrants registry takedown.

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)

aa316875bcf3fb2f59289a42cce758fa48fae241b1f11cce2a4fc97795c2366d

c011964f9503dad45858ba2fdd5de1303275d7a0a680e2c482c3e14d90c4e33c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for yangming8 (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 yangming8 across your stack and pipelines.
If you installed it — respond
yangming8 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If yangming8 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 yangming8 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. yangming8 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-f3hv-h6vj-6j6rIN-MAL-2026-017533

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks yangming8-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database