Malicious Code Injection in modest_squid-notthedevs: A Threat to npm Packages

modest_squid-notthedevs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105939: Malicious code in modest_squid-notthedevs (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

modest_squid-notthedevs is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the modest_squid-notthedevs package. This payload is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names, often themed around Indonesian culture. The continuous republishing of these variants can lead to a significant pollution of the npm registry, undermining the integrity of the ecosystem and potentially exposing users to further risks.

How To Fix

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

npm uninstall modest_squid-notthedevs

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 avoid using the modest_squid-notthedevs package and replace it with a trusted alternative. Always validate the packages you intend to use by checking their reputation and community feedback.

Conclusion

The modest_squid-notthedevs package poses a significant risk due to its malicious code designed to manipulate package metadata and republish variants. It is essential for developers to remove this package and monitor their dependencies regularly to maintain the integrity of their applications.

See every vulnerability recorded for modest_squid-notthedevs →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, potentially affecting other packages and users by introducing vulnerabilities and unreliable dependencies.

You can check your package-lock.json file for any references to modest_squid-notthedevs or use tools like Vulert to monitor your dependencies for vulnerabilities.

Immediately uninstall the package using 'npm uninstall modest_squid-notthedevs' and replace it with a trusted alternative.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

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

How To Fix

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

npm uninstall modest_squid-notthedevs

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