MalwarePublished 10 Nov 2025

umi-kue77-breki (npm) · Malicious Code

Affects umi-kue77-brekiSource GCVE Database

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

Data as of 5 Nov 2026, 08:39 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-52552

What to do

Remove umi-kue77-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
npmumi-kue77-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 umi-kue77-breki contains malicious code linked to a large-scale spam campaign associated with tea.xyz token rewards. This campaign involves autopublish scripts that automatically generate and publish numerous derivative packages with randomized Indonesian-themed names. The malicious payload modifies package.json files to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry and inflating developer reputation scores.

Impact

The malicious package causes pollution of the npm registry by generating numerous derivative packages with randomized names, which can degrade the quality and trustworthiness of the npm ecosystem. It manipulates package metadata to bypass private flags and enables continuous republishing, potentially misleading developers and automated systems relying on npm package data. There is no indication of direct exploitation or compromise of user systems beyond the registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid using the umi-kue77-breki package and related derivative packages. Registry maintainers and security teams should monitor for and remove such spam packages to maintain ecosystem integrity. Since this is a registry pollution and reputation manipulation campaign, standard package vetting and source verification practices are recommended.

Summary

The umi-kue77-breki npm package is part of a widespread malicious campaign flooding the npm registry with over 15,000 spam packages in 2024. These packages include autopublish scripts (such as auto.js and autopublish.js variants) that automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json by removing private flags and changing version numbers to enable continuous republishing. This activity aims to manipulate developer reputation scores for the tea protocol token rewards and results in significant pollution of the npm ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 08:39 UTC

Technical details

Community reviews