MalwarePublished 10 Nov 2025

dono-kue2-sukiwir (npm) · Malicious Code

Affects dono-kue2-sukiwirSource GCVE Database

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

Data as of 10 Nov 2026, 16:44 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55932

What to do

Remove dono-kue2-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-kue2-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-kue2-sukiwir' 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 to inflate developer reputation scores and pollute the npm registry.

Impact

The malicious package enables automated republishing of numerous derivative packages, which can pollute the npm registry and distort developer reputation metrics. While no direct exploitation or compromise of user systems is described, the manipulation undermines the integrity of the npm ecosystem and may mislead users relying on package reputations.

Defensive guidance

Mitigation involves avoiding use of the affected package and related variants. Registry maintainers and npm users should monitor for and remove such malicious packages to prevent ecosystem pollution. Users should verify package authenticity and avoid packages linked to the tea.xyz token reward campaign.

Summary

This threat involves the 'dono-kue2-sukiwir' npm package, which is associated with the tea.xyz token reward campaign. 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 code alters package.json by removing private flags and modifying version numbers, facilitating repeated republishing of variants. This activity aims to manipulate developer reputation scores for tea protocol token rewards and results in npm registry pollution.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews