MalwarePublished 10 Nov 2025

eka-brengkes76-sukiwir (npm) · Malicious Code

Affects eka-brengkes76-sukiwirSource GCVE Database

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

Data as of 10 Nov 2026, 16:48 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55971

What to do

Remove eka-brengkes76-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
npmeka-brengkes76-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 eka-brengkes76-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, change version numbers, and continuously republish variants, polluting the npm registry.

Impact

The malicious payload can lead to pollution of the npm registry with numerous derivative packages, potentially misleading developers and automated systems that rely on npm package metadata. It may also distort developer reputation scores within the tea protocol token reward system. There is no direct evidence of exploitation or compromise of end-user systems reported in the data.

Defensive guidance

Since this is a malicious package campaign, the recommended action is to avoid using the affected package and its derivatives. Registry maintainers and security teams should monitor and remove such packages to prevent ecosystem pollution. Users should verify package authenticity and provenance before installation.

Summary

This threat involves the npm package eka-brengkes76-sukiwir, which is associated with the tea.xyz token reward campaign that flooded the npm ecosystem. The package includes autopublish scripts (such as auto.js and autopublish.js) that automate the creation and publication of derivative packages with randomized names. These scripts alter package.json by removing private flags and modifying version numbers to enable continuous republishing. The purpose is to inflate developer reputation scores for the tea protocol token rewards and to pollute the npm registry with numerous variants.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews