Malicious Code Injection in amazing_crab_z3n Package - npm Vulnerability

amazing_crab_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99391: Malicious code in amazing_crab_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The amazing_crab_z3n package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can lead to inflated developer reputation scores. However, this functionality has been exploited to introduce malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the amazing_crab_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry with derivative packages, potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious payload can affect the integrity of applications relying on this package, making them susceptible to further attacks or misuse.

How To Fix

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

npm uninstall amazing_crab_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 temporary workaround, you can remove the amazing_crab_z3n package from your project by executing the following command: npm uninstall amazing_crab_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The amazing_crab_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to ensure ongoing security.

See every vulnerability recorded for amazing_crab_z3n →

Share this vulnerability

FAQ

The amazing_crab_z3n package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automated publication of derivative packages.

The vulnerability can compromise the integrity of your application by introducing malicious code that modifies package configurations and potentially exposes your application to further security risks.

If you have installed the amazing_crab_z3n package, it is crucial to uninstall it immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

Regularly update your dependencies to their latest versions, review security advisories, and utilize tools like Vulert to monitor your project for vulnerabilities.

How To Fix

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

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