MalwarePublished 10 Nov 2025

cindy-kemplang75-ruro (npm) · Malicious Code

Affects cindy-kemplang75-ruroSource GCVE Database

Malicious package : remove cindy-kemplang75-ruro and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 07:46 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-51345

What to do

Remove cindy-kemplang75-ruro 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
npmcindy-kemplang75-ruro	Affected–	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 cindy-kemplang75-ruro contains malicious code as part of a large-scale spam campaign linked to tea.xyz token rewards. It includes autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and increment version numbers, enabling continuous republishing to pollute the npm registry and inflate developer reputation scores.

Impact

This malicious package can degrade the integrity of the npm registry by flooding it with spam packages, potentially misleading developers and automated systems that rely on package metadata. It manipulates package metadata to bypass privacy flags and repeatedly publishes variants, which may contribute to reputation inflation and ecosystem pollution. There is no indication of direct exploitation or compromise of end-user systems beyond registry pollution.

Defensive guidance

The best mitigation is to avoid using or depending on the cindy-kemplang75-ruro package and other related spam packages from the tea.xyz campaign. Registry maintainers and security teams should monitor and remove such malicious packages to preserve ecosystem integrity.

Summary

The cindy-kemplang75-ruro npm package is identified as malicious within a campaign that flooded npm with over 15,000 spam packages in 2024. These packages use autopublish scripts (e.g., auto.js, autopublish.js) to automatically create and publish derivative packages with randomized names. The malicious code alters package.json by removing private flags and changing version numbers, facilitating repeated republishing of variants. This activity aims to manipulate developer reputation scores associated with the tea protocol token rewards and pollutes the npm ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 07:46 UTC

Technical details

Community reviews