Malicious Code Injection in safe_clam-teagooddev Package

safe_clam-teagooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108329: Malicious code in safe_clam-teagooddev (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 safe_clam-teagooddev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the safe_clam-teagooddev package. This code is designed to manipulate the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores by continuously republishing these variants, which leads to pollution of the npm registry. This can have severe ramifications, including the potential for unauthorized access to sensitive data and the introduction of further vulnerabilities into dependent applications.

How To Fix

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

npm uninstall safe_clam-teagooddev

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 remove the safe_clam-teagooddev package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall safe_clam-teagooddev.

Conclusion

The safe_clam-teagooddev package has been identified as containing malicious code that poses significant risks to applications relying on it. Immediate action is required to update or remove the package to safeguard your application from potential threats. Utilizing tools like Vulert can further enhance your security posture by providing real-time vulnerability monitoring.

See every vulnerability recorded for safe_clam-teagooddev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate interactions with the tea protocol.

The malicious code can modify your package.json file, potentially leading to unauthorized access and further vulnerabilities in your application.

You should immediately update or uninstall the safe_clam-teagooddev package to mitigate the risks associated with this vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall safe_clam-teagooddev

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