MalwarePublished 10 Nov 2025

bitter_guan_z3n (npm) · Malicious Code

Affects bitter_guan_z3nSource GCVE Database

Malicious package : remove bitter_guan_z3n and rotate any secrets on hosts that installed it.

Data as of 8 Nov 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55406

What to do

Remove bitter_guan_z3n 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
npmbitter_guan_z3n	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 bitter_guan_z3n 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 change version numbers, enabling continuous republishing to inflate developer reputation scores and pollute the npm registry.

Impact

The malicious package undermines the integrity of the npm registry by flooding it with numerous derivative packages, which can distort developer reputation metrics and potentially mislead users relying on package metadata. This activity can degrade trust in the npm ecosystem and complicate package management and security assessments.

Defensive guidance

Mitigation involves avoiding use of the bitter_guan_z3n package and related variants. Registry maintainers and security teams should monitor for and remove such autopublished malicious packages to maintain repository integrity.

Summary

This threat involves the bitter_guan_z3n package on npm, which is associated with the tea.xyz token reward campaign. The package includes malicious autopublish scripts (e.g., auto.js, 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, facilitating repeated republishing of variants. The objective is to manipulate developer reputation scores to gain token rewards and to flood the npm registry with these packages, thereby polluting the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Nov 2026, 15:56 UTC

Technical details

Community reviews