MalwarePublished 10 Nov 2025

maya-kue17-sukiwir (npm) · Malicious Code

Affects maya-kue17-sukiwirSource GCVE Database

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

Data as of 5 Nov 2026, 11:35 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53353

What to do

Remove maya-kue17-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
npmmaya-kue17-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 maya-kue17-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 changes version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.

Impact

This malicious package campaign compromises the integrity of the npm registry by flooding it with numerous derivative packages that are automatically republished. It undermines trust in package authenticity and developer reputation scores within the npm ecosystem. While no direct exploitation or code execution impact is described, the manipulation of package metadata and registry pollution can disrupt legitimate package management and ecosystem reliability.

Defensive guidance

Users and maintainers should avoid installing packages associated with the tea.xyz token reward campaign, including maya-kue17-sukiwir. Registry maintainers should monitor and remove such autopublished malicious packages to preserve ecosystem integrity.

Summary

The maya-kue17-sukiwir npm package is involved in a token reward campaign flooding the npm ecosystem with malicious packages. It uses autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) to automatically create and publish derivative packages with randomized names. The malicious code alters package.json by removing private flags and incrementing version numbers to enable repeated republishing. This behavior aims to inflate developer reputation scores for the tea protocol token rewards and results in registry pollution.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 11:35 UTC

Technical details

Community reviews