MalwarePublished 10 Nov 2025

dewanto-toge21-ruro (npm) · Malicious Code

Affects dewanto-toge21-ruroSource GCVE Database

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

Data as of 4 Nov 2026, 19:51 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-50203

What to do

Remove dewanto-toge21-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
npmdewanto-toge21-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 dewanto-toge21-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, alters version numbers, and continuously republishes variants to pollute the npm registry and inflate developer reputation scores.

Impact

This malicious package contributes to registry pollution by flooding npm with spam packages, which can degrade the quality and trustworthiness of the npm ecosystem. It manipulates package metadata to bypass restrictions and continuously republish variants, potentially misleading developers and automated systems that rely on reputation scores. There is no indication of direct exploitation or compromise of end-user systems from this package alone.

Defensive guidance

The recommended action is to avoid using the dewanto-toge21-ruro package and related derivative packages. Registry maintainers and npm administrators should continue to monitor and remove such spam packages to maintain ecosystem integrity.

Summary

The dewanto-toge21-ruro package is identified as malicious due to embedded autopublish scripts that automate the creation and publication of numerous derivative npm packages with randomized names. This activity is part of the tea.xyz token reward campaign that flooded npm with over 15,000 spam packages in 2024. The malicious code modifies package.json by removing private flags and changing version numbers to enable continuous republishing, thereby polluting the npm registry and artificially inflating developer reputation metrics associated with the tea protocol token rewards.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 19:51 UTC

Technical details

Community reviews