MalwarePublished 11 Nov 2025

advisory_pheasant_z3n (npm) · Malicious Code

Affects advisory_pheasant_z3nSource GCVE Database

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

Data as of 11 Nov 2026, 22:21 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-131943

What to do

Remove advisory_pheasant_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
npmadvisory_pheasant_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 advisory_pheasant_z3n npm package is part of a malicious campaign linked to the tea.xyz token reward scheme. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants with Indonesian-themed or English names, polluting the npm registry.

Impact

The malicious packages pollute the npm registry by continuously publishing numerous derivative packages with randomized names. This can degrade the quality and trustworthiness of the npm ecosystem and potentially mislead users or automated systems relying on package metadata. There is no indication of direct exploitation or compromise of user systems from the provided data.

Defensive guidance

Users and maintainers should avoid using packages related to the tea.xyz token reward campaign and monitor for suspicious autopublish scripts in npm packages. Registry maintainers should consider removing or blocking these malicious packages to prevent ecosystem pollution.

Summary

This threat involves malicious npm packages associated with the tea.xyz token reward campaign. The packages include autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json to remove private flags and changes version numbers to enable repeated publication. The campaign's goal is to inflate developer reputation scores by flooding the npm registry with numerous variants, thereby polluting the ecosystem.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 22:21 UTC

Technical details

Community reviews