MalwarePublished 10 Nov 2025

monthly_aardvark_z3n (npm) · Malicious Code

Affects monthly_aardvark_z3nSource GCVE Database

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

Data as of 10 Nov 2026, 16:21 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-60891

What to do

Remove monthly_aardvark_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
npmmonthly_aardvark_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 'monthly_aardvark_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 Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants to pollute the npm registry.

Impact

The malicious package pollutes the npm registry with numerous derivative packages, potentially misleading developers and automated systems relying on package metadata. It inflates developer reputation scores fraudulently within the tea protocol token reward system. There is no evidence of direct exploitation or compromise of end-user systems documented.

Defensive guidance

Users and maintainers should avoid installing or depending on packages linked to this campaign. Registry maintainers may consider removing or blocking these packages to prevent further pollution. Monitor npm packages for suspicious autopublish scripts and randomized naming patterns.

Summary

This threat involves a malicious npm package named 'monthly_aardvark_z3n' associated with the tea.xyz token reward campaign. The package includes autopublish scripts (e.g., auto.js, autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code alters package.json by removing private flags and modifying version numbers, facilitating repeated republishing of variants. This behavior aims to inflate developer reputation scores within the tea protocol token ecosystem and results in registry pollution. There is no information about active exploitation or CVSS scoring.

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

Community reviews