MalwarePublished 10 Nov 2025

brilliant_locust_z3n (npm) · Malicious Code

Affects brilliant_locust_z3nSource GCVE Database

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

Data as of 8 Nov 2026, 15:57 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55420

What to do

Remove brilliant_locust_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
npmbrilliant_locust_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 brilliant_locust_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 alter version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and artificially inflates developer reputation scores for the tea protocol token rewards.

Impact

The malicious payload enables continuous automated publishing of derivative npm packages, which pollutes the npm registry and artificially inflates developer reputation scores. This can undermine trust in the npm ecosystem and potentially mislead users or automated systems relying on reputation metrics. There is no indication of direct exploitation or compromise beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid using the brilliant_locust_z3n package and related variants. Registry maintainers should monitor and remove such autopublished malicious packages to maintain ecosystem integrity.

Summary

This threat involves the brilliant_locust_z3n npm package, which is used in a token reward campaign flooding the npm ecosystem. 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 code modifies package.json by removing private flags and changing version numbers to facilitate repeated republishing. The purpose is to inflate developer reputation scores within the tea.xyz token reward system and to pollute the npm registry with numerous variants.

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Nov 2026, 15:57 UTC

Technical details

Community reviews