MalwarePublished 10 Nov 2025

iwan-rendang46-riris (npm) · Malicious Code

Affects iwan-rendang46-ririsSource GCVE Database

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

Data as of 5 Nov 2026, 09:32 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53786

What to do

Remove iwan-rendang46-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
npmiwan-rendang46-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 iwan-rendang46-riris 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 to inflate developer reputation scores and pollute the npm registry.

Impact

The malicious package enables automated generation and publication of numerous derivative npm packages, which can distort developer reputation scores and degrade the integrity of the npm registry by flooding it with spam packages. This undermines trust in the package ecosystem and may complicate package management and security for users relying on npm.

Defensive guidance

Users and maintainers should avoid installing or depending on the iwan-rendang46-riris package and related variants. Registry maintainers should consider removing these packages and implementing controls to detect and block automated spam publishing activities.

Summary

This threat involves the npm package iwan-rendang46-riris, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (e.g., auto.js, autopublish.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 variants. This behavior aims to manipulate developer reputation metrics and flood the npm registry with numerous packages, thereby polluting the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 09:32 UTC

Technical details

Community reviews