MalwarePublished 10 Nov 2025

mixed_elk_z3n (npm) · Malicious Code

Affects mixed_elk_z3nSource GCVE Database

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

Data as of 10 Nov 2026, 16:32 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-60873

What to do

Remove mixed_elk_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
npmmixed_elk_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 mixed_elk_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 changes version numbers, enabling continuous republishing of variants. This behavior pollutes the npm registry and inflates developer reputation scores fraudulently.

Impact

The malicious package pollutes the npm registry with numerous derivative packages, potentially misleading developers and automated systems relying on npm metadata. It inflates developer reputation scores fraudulently, which could undermine trust in the npm ecosystem. There is no indication of direct exploitation or compromise of user systems from this package alone.

Defensive guidance

Users and maintainers should avoid installing or depending on packages associated with the tea.xyz token reward campaign or those exhibiting autopublish scripts with randomized naming patterns. Registry maintainers should monitor and remove such malicious packages to protect the ecosystem.

Summary

This threat involves the mixed_elk_z3n npm package, which is associated with the tea.xyz token reward campaign. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automate the creation and publication of derivative packages with randomized names. The malicious payload alters package.json by removing private flags and modifying version numbers, facilitating ongoing republishing of variants. The intent is to flood the npm registry with these packages to manipulate developer reputation scores for tea protocol token rewards.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 16:32 UTC

Technical details

Community reviews