MalwarePublished 10 Nov 2025

casual_crane_z3n (npm) · Malicious Code

Affects casual_crane_z3nSource GCVE Database

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

Data as of 8 Nov 2026, 16:04 UTC

Classification

Malicious package

Published to npm · OSV MAL-2025-55523

What to do

Remove casual_crane_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
npmcasual_crane_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 casual_crane_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. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.

Impact

This malicious activity results in the pollution of the npm registry with numerous derivative packages, which can undermine the integrity of the ecosystem. It also enables fraudulent inflation of developer reputation scores within the tea.xyz token reward system. There is no direct evidence of exploitation beyond registry pollution and reputation manipulation.

Defensive guidance

Users and maintainers should avoid installing or trusting packages linked to this campaign. Registry maintainers may consider removing or blocking these packages to prevent further pollution. Monitoring for similar autopublish scripts in npm packages can help identify related malicious activity.

Summary

The casual_crane_z3n npm package is associated with the tea.xyz token reward campaign that flooded the npm ecosystem with malicious packages. These packages include autopublish scripts (such as auto.js and autopublish.js) that automate the creation and publication of derivative packages with randomized names. The malicious code modifies package.json by removing private flags and altering version numbers to facilitate repeated republishing. The intent is to inflate developer reputation scores within the tea protocol token rewards 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, 16:04 UTC

Technical details

Community reviews