MalwarePublished 10 Nov 2025

grateful_peafowl_z3n (npm) · Malicious Code

Affects grateful_peafowl_z3nSource GCVE Database

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

Data as of 10 Nov 2026, 17:35 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-56560

What to do

Remove grateful_peafowl_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
npmgrateful_peafowl_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 grateful_peafowl_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 of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.

Impact

The malicious payload causes pollution of the npm registry by continuously publishing numerous derivative packages with randomized names. This can degrade the quality and trustworthiness of the npm ecosystem and may mislead users or automated systems relying on reputation scores. There is no direct evidence of exploitation in the wild or further technical impact such as code execution or data compromise described.

Defensive guidance

Users and maintainers should avoid using or depending on packages linked to this campaign, including grateful_peafowl_z3n. Registry maintainers should monitor and remove such autopublished malicious packages to preserve ecosystem integrity.

Summary

This threat involves the grateful_peafowl_z3n npm package, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (such as auto.js and autopublish.js variants) that automate the creation and publication of derivative npm packages with randomized names. The malicious code alters package.json files by removing private flags and modifying version numbers, facilitating repeated republishing of these variants. The objective is to flood the npm registry with these packages to artificially boost developer reputation scores within the tea protocol token ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 17:35 UTC

Technical details

Community reviews