MalwarePublished 11 Nov 2025

cruel_tern_z3n (npm) · Malicious Code

Affects cruel_tern_z3nSource GCVE Database

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

Data as of 11 Nov 2026, 23:16 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-132651

What to do

Remove cruel_tern_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
npmcruel_tern_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 npm package 'cruel_tern_z3n' 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 names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, changes version numbers, and generates random Indonesian-themed or English package names. This activity results in continuous republishing of variants, polluting the npm registry.

Impact

This malicious activity pollutes the npm registry with numerous derivative packages, potentially undermining trust in the ecosystem. It inflates developer reputation scores fraudulently, which could mislead users or automated systems relying on reputation metrics. There is no indication of direct exploitation or compromise of user systems beyond registry pollution and reputation manipulation.

Defensive guidance

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

Summary

The 'cruel_tern_z3n' npm package is involved in a token reward campaign flooding the npm ecosystem. It uses autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) to automatically create and publish derivative packages with randomized names. The malicious code alters package.json by removing private flags and changing version numbers, enabling repeated publication of variants. This behavior inflates developer reputation scores for the tea protocol token rewards and causes registry pollution.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 23:16 UTC

Technical details

Community reviews