MalwarePublished 10 Nov 2025

putri-klipo92-ruro (npm) · Malicious Code

Affects putri-klipo92-ruroSource GCVE Database

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

Data as of 5 Nov 2026, 16:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54335

What to do

Remove putri-klipo92-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
npmputri-klipo92-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 putri-klipo92-ruro npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains 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 change version numbers, enabling continuous republishing of variants. This behavior pollutes the npm registry with numerous malicious or spam packages.

Impact

The primary impact is the pollution of the npm registry with numerous derivative packages that may mislead developers and automated systems. This can degrade the quality and trustworthiness of the npm ecosystem and potentially expose users to malicious code embedded in these packages. There is no evidence of active exploitation beyond registry pollution or direct compromise of users.

Defensive guidance

Users and maintainers should avoid installing or depending on packages associated with this campaign. Registry maintainers should consider removing or blocking these packages to prevent further pollution. Monitoring for and removing autopublish scripts in packages can help mitigate similar threats.

Summary

This threat involves the putri-klipo92-ruro npm package, which is associated with the tea.xyz token reward campaign that flooded the npm ecosystem. The package includes autopublish scripts (such as auto.js and autopublish.js variants) designed to automatically create and publish derivative packages with randomized names. The malicious payload manipulates package.json by removing private flags and altering version numbers, facilitating repeated publication of new variants. This results in registry pollution and attempts to inflate developer reputation scores within the tea protocol token system.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 16:56 UTC

Technical details

Community reviews