MalwarePublished 10 Nov 2025

eko-bika21-sukiwir (npm) · Malicious Code

Affects eko-bika21-sukiwirSource GCVE Database

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

Data as of 10 Nov 2026, 16:51 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-56007

What to do

Remove eko-bika21-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
npmeko-bika21-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 eko-bika21-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 to inflate developer reputation scores and pollute the npm registry.

Impact

The malicious package manipulates the npm registry by continuously publishing derivative packages with randomized names, which can degrade the quality and trustworthiness of the npm ecosystem. It inflates developer reputation scores fraudulently, potentially misleading users and automated systems that rely on these metrics. There is no direct evidence of exploitation in the wild or further payload delivery beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid installing or depending on the eko-bika21-sukiwir package and related derivative packages. Registry maintainers and security teams should monitor and remove such malicious packages to maintain ecosystem integrity.

Summary

This threat involves the npm package eko-bika21-sukiwir, which is associated with the tea.xyz token reward campaign that flooded the npm ecosystem. The package includes autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code alters package.json by removing private flags and incrementing version numbers, facilitating repeated republishing of variants. This behavior aims to manipulate developer reputation scores for token rewards and causes pollution of the npm registry with numerous derivative packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews