MalwarePublished 10 Nov 2025

dono-telurtahu28-sukiwir (npm) · Malicious Code

Affects dono-telurtahu28-sukiwirSource GCVE Database

Malicious package : remove dono-telurtahu28-sukiwir and rotate any secrets on hosts that installed it.

Data as of 10 Nov 2026, 16:46 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55950

What to do

Remove dono-telurtahu28-sukiwir 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
npmdono-telurtahu28-sukiwir	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 dono-telurtahu28-sukiwir is associated with the tea.xyz token reward campaign and contains malicious autopublish scripts. These scripts automatically generate and publish derivative packages with randomized Indonesian-themed names to inflate developer reputation scores for the tea protocol token rewards. The malicious payload modifies package.json files by removing private flags, changing version numbers, and continuously republishing variants, leading to pollution of the npm registry.

Impact

The malicious package causes pollution of the npm registry by continuously generating and publishing derivative packages with randomized names. This can degrade the quality and trustworthiness of the npm ecosystem and may mislead users or automated systems that rely on package metadata and reputation scores. There is no indication of direct exploitation or compromise of user systems beyond registry pollution and manipulation of developer reputation metrics.

Defensive guidance

Mitigation involves avoiding use or installation of this package and related derivative packages. Registry maintainers and npm administrators should consider removing or blocking these malicious packages to prevent further pollution. Developers should verify package authenticity and metadata before use.

Summary

This threat involves a malicious npm package that is part of a broader campaign flooding the npm registry with autopublished derivative packages. The autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) automate the creation and publication of new packages with randomized names, manipulating package metadata such as removing private flags and altering version numbers. The intent is to artificially inflate developer reputation scores within the tea.xyz token reward ecosystem. This activity results in registry pollution and potential trust issues for npm users.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 16:46 UTC

Technical details

Community reviews