MalwarePublished 10 Nov 2025

rifqi-buburayam23-riris (npm) · Malicious Code

Affects rifqi-buburayam23-ririsSource GCVE Database

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

Data as of 6 Nov 2026, 18:58 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54599

What to do

Remove rifqi-buburayam23-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
npmrifqi-buburayam23-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 'rifqi-buburayam23-riris' is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish numerous derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and alter version numbers, enabling continuous republishing and polluting the npm registry.

Impact

The impact is primarily the pollution of the npm registry with numerous derivative packages, which can degrade the quality and trustworthiness of the registry. It may also distort developer reputation metrics tied to the tea.xyz token reward campaign. There is no indication of direct exploitation or compromise of user systems from this package alone.

Defensive guidance

Users and maintainers should avoid installing or depending on this package and related variants. Registry maintainers should consider removing these packages and implementing controls to detect and prevent autopublishing abuse. Monitoring for and blocking packages exhibiting similar autopublish behavior is recommended.

Summary

This threat involves a malicious npm package that is used to inflate developer reputation scores for the tea protocol token rewards by flooding the npm registry with derivative packages. The package includes autopublish scripts (such as auto.js and autopublish.js variants) that automate the creation and publication of new packages with randomized names. The malicious code modifies package.json to remove privacy flags and change version numbers, facilitating repeated republishing of variants. This activity results in registry pollution and potential abuse of the npm ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 18:58 UTC

Technical details

Community reviews