Malicious Code Injection in nosy_eel-tool: A Threat to npm Packages

nosy_eel-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106383: Malicious code in nosy_eel-tool (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

nosy_eel-tool is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The malicious nature of this package compromises the integrity of the npm ecosystem, making it crucial for developers to be aware of its risks.

Vulnerability Detail

The nosy_eel-tool package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a significant risk of dependency confusion and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall nosy_eel-tool

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 monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.

Conclusion

The nosy_eel-tool package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in their dependencies.

See every vulnerability recorded for nosy_eel-tool →

Share this vulnerability

FAQ

nosy_eel-tool is an npm package identified as part of a malicious campaign that automates the generation of derivative packages to inflate developer reputation scores.

The vulnerability can lead to dependency confusion, where your application may unintentionally rely on malicious packages, compromising its security and integrity.

You should uninstall the nosy_eel-tool package immediately using the command 'npm uninstall nosy_eel-tool' to mitigate any risks.

You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

No, the nosy_eel-tool package is considered malicious and should be removed rather than patched.

How To Fix

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

npm uninstall nosy_eel-tool

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