Malicious Code Injection in chet-teadev Package - npm Vulnerability

chet-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100377: Malicious code in chet-teadev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The chet-teadev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the chet-teadev package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The malicious payload can affect developers' reputations and lead to unintended consequences in software projects.

How To Fix

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

npm uninstall chet-teadev

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 chet-teadev package and replace it with a similar, trusted package that provides the required functionality. Always review the packages you include in your project for any known vulnerabilities.

Conclusion

The chet-teadev package poses a significant risk due to its malicious code that modifies project files and repopulates the npm registry with unwanted packages. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for chet-teadev →

Share this vulnerability

FAQ

The chet-teadev package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious code.

You should uninstall the chet-teadev package immediately using 'npm uninstall chet-teadev' and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your project for open-source vulnerabilities in real-time using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, be cautious of packages that are part of the tea.xyz token reward campaign or exhibit similar behavior of auto-publishing and modifying package metadata.

How To Fix

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

npm uninstall chet-teadev

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