Malicious Code Injection in Surprising Squid Dumbs Package

surprising_squid_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109350: Malicious code in surprising_squid_dumbs (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'surprising_squid_dumbs' package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its primary functionality is compromised, making it a significant threat to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious design of the 'surprising_squid_dumbs' package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The ramifications include loss of trust in the npm ecosystem, potential security risks for applications using this package, and a cluttered registry that makes it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall surprising_squid_dumbs

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 'surprising_squid_dumbs' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can lock your package versions in package.json to prevent automatic updates to potentially malicious versions.

Conclusion

The 'surprising_squid_dumbs' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for surprising_squid_dumbs →

Share this vulnerability

FAQ

It is a malicious npm package designed to manipulate the npm registry by generating and publishing derivative packages.

Using this package can compromise your application's integrity and expose it to security risks due to the malicious behavior of the package.

You should remove the 'surprising_squid_dumbs' package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall surprising_squid_dumbs

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