MalwarePublished 10 Nov 2025

kiki-bakwan10-sukiwir (npm) · Malicious Code

Affects kiki-bakwan10-sukiwirSource GCVE Database

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

Data as of 10 Nov 2026, 18:19 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-57122

What to do

Remove kiki-bakwan10-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
npmkiki-bakwan10-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 'kiki-bakwan10-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, changes version numbers, and continuously republishes variants to pollute the npm registry.

Impact

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

Defensive guidance

Users and maintainers should avoid installing or depending on this package and related variants. Registry maintainers should consider removing these packages and monitoring for similar autopublish scripts to prevent further pollution.

Summary

This threat involves a malicious npm package that participates in the tea.xyz token reward campaign. The package includes autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of numerous derivative packages with randomized names. The malicious code alters package.json by removing private flags and incrementing version numbers to evade detection and inflate developer reputation scores. This results in a flood of packages in the npm registry, potentially undermining the integrity of the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 18:19 UTC

Technical details

Community reviews