MalwarePublished 10 Nov 2025

rifqi-ruwet48-sluey (npm) · Malicious Code

Affects rifqi-ruwet48-slueySource GCVE Database

Malicious package : remove rifqi-ruwet48-sluey and rotate any secrets on hosts that installed it.

Data as of 6 Nov 2026, 19:02 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54650

What to do

Remove rifqi-ruwet48-sluey 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
npmrifqi-ruwet48-sluey	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 'rifqi-ruwet48-sluey' 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. These scripts modify package.json files to remove private flags and alter version numbers, enabling continuous republishing to inflate developer reputation scores and pollute the npm registry.

Impact

The malicious package undermines the integrity of the npm registry by flooding it with numerous derivative packages that bypass privacy settings and manipulate versioning. This can lead to inflated developer reputation scores, misleading metrics, and potential trust erosion in the npm ecosystem. While no direct exploitation or code execution impact is described, the campaign's automated republishing behavior can disrupt package management and ecosystem reliability.

Defensive guidance

The best mitigation is to avoid using packages associated with this campaign and to monitor and remove such packages from internal repositories. Registry maintainers should continue to identify and remove these malicious packages to prevent ecosystem pollution.

Summary

This threat involves a malicious npm package that is part of a broader campaign flooding the npm registry with auto-generated derivative packages. The malicious payload includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that modify package metadata to remove privacy restrictions and manipulate versioning. The scripts generate randomized package names, primarily Indonesian-themed, and repeatedly publish these variants to artificially boost developer reputation scores associated with the tea.xyz token reward system. This activity results in registry pollution and potential trust issues within the npm ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews