Malicious Code Injection in additional_worm-appteadev Package

additional_worm-appteadev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99129: Malicious code in additional_worm-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The additional_worm-appteadev package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish itself, contributing to the pollution of the npm registry.

Vulnerability Detail

The vulnerability in the additional_worm-appteadev package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate the npm ecosystem.

How To Fix

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

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

Conclusion

The additional_worm-appteadev package poses a significant risk due to its malicious code that alters package files and repopulates the npm registry with compromised versions. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for additional_worm-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the modification of your package.json file and the introduction of malicious code, which can compromise your project's integrity.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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