MalwarePublished 10 Nov 2025

siska-nasipecel77-breki (npm) · Malicious Code

Affects siska-nasipecel77-brekiSource GCVE Database

Malicious package : remove siska-nasipecel77-breki and rotate any secrets on hosts that installed it.

Data as of 6 Nov 2026, 19:23 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54921

What to do

Remove siska-nasipecel77-breki 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
npmsiska-nasipecel77-breki	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 'siska-nasipecel77-breki' 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, alters version numbers, and continuously republishes variants to pollute the npm registry.

Impact

The malicious package pollutes the npm registry with numerous derivative packages, potentially misleading developers and automated systems that rely on package metadata and reputation. It may degrade the integrity of the npm ecosystem by inflating reputation scores fraudulently and increasing noise in package searches and dependency graphs. There is no indication of direct exploitation or code execution impact beyond registry pollution.

Defensive guidance

Mitigation involves avoiding use of packages associated with the tea.xyz token reward campaign and monitoring for suspicious autopublish scripts in npm packages. Registry maintainers and security teams should consider removing or blocking such packages to prevent ecosystem pollution.

Summary

This threat involves a malicious npm package used in a token reward campaign flooding the npm registry. 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. These scripts modify package.json by removing private flags and changing version numbers to enable continuous republishing. The campaign aims to inflate developer reputation scores for the tea protocol token rewards by polluting the npm registry with numerous variants.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 19:23 UTC

Technical details

Community reviews