MalwarePublished 10 Nov 2025

iwan-nasisayur97-sluey (npm) · Malicious Code

Affects iwan-nasisayur97-slueySource GCVE Database

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

Data as of 5 Nov 2026, 09:33 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53781

What to do

Remove iwan-nasisayur97-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
npmiwan-nasisayur97-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 'iwan-nasisayur97-sluey' is part of a malicious campaign linked to the tea.xyz token reward scheme. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. These scripts modify package.json files to remove private flags and alter version numbers, enabling continuous republishing of variants. This activity aims to inflate developer reputation scores and pollutes the npm registry with malicious packages.

Impact

The malicious package pollutes the npm registry with numerous derivative packages, potentially misleading developers and automated systems relying on package metadata. It manipulates developer reputation scores within the tea protocol token reward system. While no direct exploitation or code execution impact is described, the presence of such packages can degrade trust in the npm ecosystem and may lead to indirect security risks if developers inadvertently use these packages.

Defensive guidance

Users and maintainers should avoid using packages associated with this campaign. Registry maintainers should consider removing these malicious packages and monitoring for similar autopublish scripts. Developers should verify package authenticity and metadata before use. Since this is a registry pollution and reputation manipulation campaign, standard package vetting and repository hygiene are recommended.

Summary

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

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews