MalwarePublished 10 Nov 2025

rina-gorengan35-sluey (npm) · Malicious Code

Affects rina-gorengan35-slueySource GCVE Database

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

Data as of 6 Nov 2026, 19:04 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54681

What to do

Remove rina-gorengan35-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
npmrina-gorengan35-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 'rina-gorengan35-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. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants to pollute the npm registry.

Impact

The malicious package can pollute the npm registry with numerous derivative packages, potentially undermining the integrity of the ecosystem and misleading users or automated systems relying on package metadata. It inflates developer reputation scores fraudulently, which could affect trust and token reward mechanisms. 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 trusting packages associated with this campaign. Registry maintainers should consider removing or blocking such packages to prevent ecosystem pollution. Monitoring for packages with similar autopublish scripts and randomized naming patterns is advised.

Summary

This threat involves a malicious npm package that is used in a token reward campaign flooding the npm ecosystem. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) which automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json by removing private flags and changing version numbers to enable repeated publication. This behavior inflates developer reputation scores for the tea protocol token rewards and results in registry pollution through numerous variants.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews