MalwarePublished 10 Nov 2025

sinta-bakwan100-ruro (npm) · Malicious Code

Affects sinta-bakwan100-ruroSource GCVE Database

Malicious package : remove sinta-bakwan100-ruro and rotate any secrets on hosts that installed it.

Data as of 6 Nov 2026, 19:18 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54834

What to do

Remove sinta-bakwan100-ruro 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
npmsinta-bakwan100-ruro	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 sinta-bakwan100-ruro 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 of variants to pollute the npm registry.

Impact

The malicious package pollutes the npm registry by continuously publishing derivative packages with randomized names, which can undermine the integrity of the npm ecosystem and mislead users relying on package metadata and reputation scores. It may also distort developer reputation metrics tied to the tea.xyz token reward system.

Defensive guidance

Users and maintainers should avoid installing or trusting packages linked to this campaign. Registry maintainers should consider removing or blocking these packages to prevent further pollution. Monitoring for packages with similar autopublish scripts and randomized naming patterns is recommended.

Summary

This threat involves the npm package sinta-bakwan100-ruro, which is associated with the tea.xyz token reward campaign. The package includes malicious autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. These scripts alter package.json by removing private flags and incrementing version numbers, facilitating repeated republishing of variants. The intent is to inflate developer reputation scores and flood the npm registry with polluted packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews