Malicious Code Injection in everette-teadev Package: A Threat to npm Ecosystem

everette-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102277: Malicious code in everette-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The everette-teadev 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 function of this package is to facilitate the generation and publication of derivative packages, but it has been compromised to include harmful scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability in the everette-teadev package stems from its malicious code, which is designed to modify the package.json file by removing private flags and altering version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, posing significant risks to developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall everette-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 remove the everette-teadev package from your project by executing the following command: npm uninstall everette-teadev. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The everette-teadev package poses a significant threat due to its malicious code designed to manipulate package metadata and clutter the npm registry. It is crucial for developers to stay vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for everette-teadev →

Share this vulnerability

FAQ

The everette-teadev package is an npm package associated with a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and cluttering the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you have installed the everette-teadev package, it is recommended to uninstall it immediately and check for any updates or patches.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions to minimize risks.

How To Fix

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

npm uninstall everette-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