Malicious Code Injection in valid_earwig-appteadev Package

valid_earwig-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110321: Malicious code in valid_earwig-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 valid_earwig-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate specific functionalities within the application. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, compromising its integrity and security.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to manipulate package metadata. These scripts, including auto.js and autopublish.js, are designed to remove private flags from package.json, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry, posing a significant risk to developers and users relying on this package.

How To Fix

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

npm uninstall valid_earwig-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 temporary workaround, you can avoid using the valid_earwig-appteadev package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any vulnerabilities using tools like Vulert.

Conclusion

The valid_earwig-appteadev package has been identified as containing malicious code that can compromise the integrity of applications using it. It is essential to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying such vulnerabilities in the future.

See every vulnerability recorded for valid_earwig-appteadev →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can lead to unauthorized modifications in your package.json file and may compromise the security of your application.

You should uninstall the valid_earwig-appteadev package immediately and monitor for any updates or patches.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

Vulert is a tool that monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

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