MalwarePublished 10 Nov 2025

fadhil-ruwet76-riris (npm) · Malicious Code

Affects fadhil-ruwet76-ririsSource GCVE Database

Malicious package : remove fadhil-ruwet76-riris and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 08:17 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-51808

What to do

Remove fadhil-ruwet76-riris 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
npmfadhil-ruwet76-riris	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 fadhil-ruwet76-riris contains malicious code as part of a large-scale spam campaign linked to tea.xyz token rewards. It uses autopublish scripts to generate and publish numerous derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and increment version numbers, enabling continuous republishing and polluting the npm registry.

Impact

This malicious package contributes to registry pollution by continuously publishing derivative packages with randomized names, which can degrade the quality and trustworthiness of the npm ecosystem. It may also distort developer reputation metrics by artificially inflating scores through the tea.xyz token reward system. There is no indication of direct exploitation or compromise of user systems beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid installing or depending on the fadhil-ruwet76-riris package and related spam packages from the tea.xyz campaign. Registry maintainers should consider removing these spam packages and monitoring for similar autopublish scripts to prevent further pollution.

Summary

The fadhil-ruwet76-riris package is identified as malicious within a campaign that flooded the npm registry with over 15,000 spam packages in 2024. These packages employ autopublish scripts (such as auto.js and autopublish3.js) to automatically create and publish derivative packages with randomized names to artificially inflate developer reputation scores for tea protocol token rewards. The malicious code alters package.json by removing private flags and changing version numbers, facilitating ongoing republishing of variants and causing registry pollution.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 08:17 UTC

Technical details

Community reviews