Malicious Code Injection in creepy_clam-toolteadev: A Threat to npm Packages

creepy_clam-toolteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101066: Malicious code in creepy_clam-toolteadev (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

creepy_clam-toolteadev is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate developers in earning token rewards through various functionalities. However, it has been compromised and is now associated with malicious activities, including the automatic generation and publication of derivative packages that can harm the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm ecosystem with spammy packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry, potentially affecting developers who rely on the integrity of package sources. The malicious payload can compromise the security of applications using this package, leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall creepy_clam-toolteadev

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 creepy_clam-toolteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The creepy_clam-toolteadev package has been identified as a source of malicious code that can compromise the integrity of npm packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for creepy_clam-toolteadev →

Share this vulnerability

FAQ

creepy_clam-toolteadev is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The vulnerability can lead to the pollution of the npm registry and compromise the security of applications that depend on this package.

You should uninstall the creepy_clam-toolteadev package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert to monitor your package dependencies for vulnerabilities in real-time without needing to access the code.

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

How To Fix

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

npm uninstall creepy_clam-toolteadev

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