Malicious Code Injection in junior_crane_z3n Package: A Threat to npm Users

junior_crane_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104732: Malicious code in junior_crane_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The junior_crane_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in the junior_crane_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aimed to exploit npm's publishing mechanisms.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall junior_crane_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, you can temporarily remove the junior_crane_z3n package from your project dependencies to mitigate the risk until a fix is available. Use the following command to uninstall the package: npm uninstall junior_crane_z3n.

Conclusion

The junior_crane_z3n package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for junior_crane_z3n →

Share this vulnerability

FAQ

The junior_crane_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if it relies on affected packages.

You should uninstall the junior_crane_z3n package immediately and monitor for any updates or patches from the package maintainers.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall junior_crane_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback