MalwarePublished 10 Nov 2025

rudi-kue52-ruro (npm) · Malicious Code

Affects rudi-kue52-ruroSource GCVE Database

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

Data as of 6 Nov 2026, 19:08 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54746

What to do

Remove rudi-kue52-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
npmrudi-kue52-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 rudi-kue52-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 to pollute the npm registry.

Impact

The malicious payload enables continuous automated publishing of derivative npm packages, which can degrade the integrity of the npm registry by flooding it with spam or potentially malicious packages. It also manipulates developer reputation scores within the tea.xyz token reward system, potentially misleading users and automated systems that rely on package metadata and reputation.

Defensive guidance

Users and maintainers should avoid installing or depending on the rudi-kue52-ruro package and related derivatives. Registry maintainers should monitor for and remove such autopublished spam packages to maintain ecosystem integrity.

Summary

This threat involves the rudi-kue52-ruro package on npm, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automate the creation and publication of derivative packages with randomized names. The malicious code alters package.json by removing private flags and modifying version numbers, facilitating repeated republishing of these variants. This activity inflates developer reputation scores fraudulently and pollutes the npm ecosystem with numerous malicious or spam packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 19:08 UTC

Technical details

Community reviews