MalwarePublished 10 Nov 2025

sinta-tek2-sluey (npm) · Malicious Code

Affects sinta-tek2-slueySource GCVE Database

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

Data as of 6 Nov 2026, 19:21 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54887

What to do

Remove sinta-tek2-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
npmsinta-tek2-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 sinta-tek2-sluey npm package 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, alter version numbers, and continuously republish variants, polluting the npm registry and inflating developer reputation scores illegitimately.

Impact

The malicious payload enables continuous republishing of npm packages with randomized names, which pollutes the npm registry and artificially inflates developer reputation scores. This undermines the integrity of the npm ecosystem and can mislead users and automated systems relying on reputation metrics. There is no indication of direct exploitation or compromise of end-user systems from this package alone.

Defensive guidance

Users and maintainers should avoid installing or trusting packages associated with this campaign. Registry maintainers should monitor and remove such autopublished malicious packages to preserve ecosystem integrity.

Summary

This threat involves the sinta-tek2-sluey npm package, 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. These scripts modify package.json by removing private flags and changing version numbers to enable repeated publication. The campaign's goal is to inflate developer reputation scores by flooding the npm registry with numerous variants, thereby polluting the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews