MalwarePublished 10 Nov 2025

putri-kue77-pore (npm) · Malicious Code

Affects putri-kue77-poreSource GCVE Database

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

Data as of 5 Nov 2026, 16:57 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-54350

What to do

Remove putri-kue77-pore 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
npmputri-kue77-pore	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 putri-kue77-pore npm package 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 to continuously republish variants, polluting the npm registry and inflating developer reputation scores.

Impact

The malicious payload causes pollution of the npm registry by generating numerous derivative packages with randomized names and altered metadata. This can undermine the integrity of the npm ecosystem and distort developer reputation scores tied to the tea protocol token rewards. There is no indication of direct exploitation or compromise of end-user systems beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid using the putri-kue77-pore package and related variants. Registry maintainers should consider removing these malicious packages to prevent further pollution. Monitoring for similar autopublish scripts in npm packages is recommended to identify and block this campaign.

Summary

This threat involves the putri-kue77-pore package on npm, which is associated with the tea.xyz token reward campaign. 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, enabling repeated publication of variants. This behavior aims to manipulate developer reputation metrics and flood the npm registry with numerous related packages.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 16:57 UTC

Technical details

Community reviews