MalwarePublished 12 Aug 2026

yangming8 (npm) · Malicious Code

Affects yangming8Source GCVE Database

Malicious package : remove yangming8 and rotate any secrets on hosts that installed it.

Data as of 12 Aug 2026, 16:37 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13846

What to do

Remove yangming8 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmyangming8	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'yangming8' version 1.0.0 contains a malicious payload in its single file index.html, which serves a fake Cloudflare verification page and then redirects users to a phishing site impersonating MicroCloud. The package does not execute code on installation or require, but abuses npm registry and CDN mirrors to host a browser-side credential phishing page. The risk to developers installing the package is minimal, but end users accessing the HTML via CDN URLs are targeted. There is no CVSS score available for this threat.

Impact

End users who load the index.html file from the 'yangming8' package via npm CDN mirrors are redirected to a phishing site designed to steal credentials by impersonating MicroCloud. Developers installing or requiring the package are not directly exposed to code execution or payload delivery. The malicious package abuses the npm ecosystem for static hosting of phishing content, potentially leading to credential theft from users. There is no evidence of active exploitation in the wild or direct system compromise from installation.

Defensive guidance

Since the malicious payload is delivered via the package's HTML file served through CDN mirrors, users and developers should avoid loading content from this package's CDN URLs. The package version 1.0.0 should be removed from the npm registry to prevent further abuse. There is no indication of code execution on installation, so removing the package from developer environments is precautionary. Rotate any credentials that may have been exposed if the phishing site was accessed. Patch status is not applicable as this is a malicious package rather than a software vulnerability with a fix.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 16:37 UTC

Technical details

References

Community reviews