Malicious Code Injection in personal_clam-appteadev Package

personal_clam-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107043: Malicious code in personal_clam-appteadev (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 personal_clam-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is not well-defined, but it appears to be involved in generating and publishing derivative packages that can inflate developer reputation scores for token rewards.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the package, which includes scripts designed to autopublish variants of itself with randomized names. The payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing these variants to pollute the npm registry. This can lead to significant security risks, including the potential for unauthorized access and manipulation of developer environments.

How To Fix

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

npm uninstall personal_clam-appteadev

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. Vulert allows you to check for vulnerabilities in your project's package-lock.json file without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The personal_clam-appteadev package poses a significant security risk due to its malicious code designed to manipulate package management processes. It is essential to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for personal_clam-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to unauthorized modifications in your project, potentially compromising security and integrity.

You should uninstall the personal_clam-appteadev package immediately to mitigate any security risks.

While many npm packages are safe, it is crucial to regularly monitor and audit your dependencies for vulnerabilities.

You can use tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall personal_clam-appteadev

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