MalwarePublished 10 Nov 2025

nurul-naget99-breki (npm) · Malicious Code

Affects nurul-naget99-brekiSource GCVE Database

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

Data as of 5 Nov 2026, 11:00 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-53552

What to do

Remove nurul-naget99-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
npmnurul-naget99-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 'nurul-naget99-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 names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, change version numbers, and create Indonesian-themed package names, continuously republishing variants to pollute the npm registry.

Impact

The malicious package can distort the npm package ecosystem by flooding it with numerous derivative packages, potentially misleading users and automated systems relying on package metadata. It manipulates developer reputation scores, which could undermine trust in the npm registry and associated token reward mechanisms. There is no indication of direct exploitation or compromise of user systems beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid installing or trusting packages associated with this campaign. Registry maintainers should consider removing or blocking these packages to prevent further pollution. Monitoring for packages exhibiting autopublish scripts and suspicious metadata changes can help identify similar threats.

Summary

This threat involves a malicious npm package used in a token reward campaign flooding 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 modifying version numbers, enabling continuous republishing of variants. This behavior aims to manipulate 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:00 UTC

Technical details

Community reviews