MalwarePublished 10 Nov 2025

sari-sroto46-remi (npm) · Malicious Code

Affects sari-sroto46-remiSource GCVE Database

Malicious package : remove sari-sroto46-remi and rotate any secrets on hosts that installed it.

Data as of 6 Nov 2026, 19:13 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54828

What to do

Remove sari-sroto46-remi 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
npmsari-sroto46-remi	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 sari-sroto46-remi 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. This behavior pollutes the npm registry and inflates developer reputation scores fraudulently.

Impact

The malicious package causes pollution of the npm registry by generating many derivative packages with randomized names and manipulated metadata. This can undermine trust in the npm ecosystem and distort developer reputation metrics. There is no indication of direct exploitation or compromise of end-user systems, but the integrity and reliability of the package repository are affected.

Defensive guidance

The recommended action is to avoid using the sari-sroto46-remi package and its derivatives. Registry maintainers and security teams should monitor and remove such malicious packages to protect the ecosystem.

Summary

This threat involves the npm package sari-sroto46-remi, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (such as auto.js and autopublish3.js) that automate the creation and publication of numerous derivative packages with randomized names. The malicious code alters package.json by removing private flags and incrementing version numbers, facilitating repeated republishing. This activity aims to manipulate developer reputation scores and flood the npm registry with numerous variants, degrading the ecosystem's integrity.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews