Malicious Code Injection in statistical_crane_z3n Package

statistical_crane_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96759: Malicious code in statistical_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The statistical_crane_z3n package is part of the npm ecosystem, typically used for statistical analysis and data manipulation. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish variants of itself with altered names and configurations.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the statistical_crane_z3n package, which includes scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself under random names, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The ramifications include the risk of unintentional use of compromised packages, leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall statistical_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, avoid using the statistical_crane_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The statistical_crane_z3n package poses significant risks due to its malicious nature, which includes modifying package configurations and republishing itself. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their applications remain secure from such vulnerabilities.

See every vulnerability recorded for statistical_crane_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the statistical_crane_z3n package immediately using the command npm uninstall statistical_crane_z3n.

Yes, using this package can lead to security breaches, as it modifies your package.json and repopulates the npm registry with potentially harmful variants.

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your software.

How To Fix

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

npm uninstall statistical_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