Malicious Code Injection in Scared Eel Z3N Package

scared_eel_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108406: Malicious code in scared_eel_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'scared_eel_z3n' package is part of the npm ecosystem, often used in various JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's package management system. It is designed to automatically generate and publish derivative packages with altered metadata, which can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the 'scared_eel_z3n' package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The origin of this vulnerability is linked to a token reward campaign that floods the npm ecosystem with harmful packages, potentially compromising the integrity of applications that depend on them.

How To Fix

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

npm uninstall scared_eel_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 measure, you can avoid using the 'scared_eel_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.

Conclusion

The 'scared_eel_z3n' package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to remove this package from your projects and monitor for any vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for scared_eel_z3n →

Share this vulnerability

FAQ

The 'scared_eel_z3n' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing harmful code into your application and compromising its security.

You should immediately uninstall the 'scared_eel_z3n' package and check for any unauthorized changes in your project files.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and monitor your project with tools like Vulert.

How To Fix

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

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