Malicious Code Injection in extended_roundworm-appteadev Package

extended_roundworm-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102413: Malicious code in extended_roundworm-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 extended_roundworm-appteadev package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the extended_roundworm-appteadev package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The primary risk is the pollution of the npm registry, which can affect developers relying on the integrity of packages and potentially introduce security risks into their applications.

How To Fix

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

npm uninstall extended_roundworm-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 measure, avoid using the extended_roundworm-appteadev package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit.

Conclusion

The extended_roundworm-appteadev package contains malicious code that poses a significant risk to developers and their applications. Immediate action is required to remove the package and prevent further issues. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in open-source software.

See every vulnerability recorded for extended_roundworm-appteadev →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially introducing security vulnerabilities into applications that depend on it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

You should uninstall the package immediately using 'npm uninstall extended_roundworm-appteadev' and check for any other dependencies that may have been affected.

Regularly audit your dependencies using tools like npm audit, and consider using services like Vulert to monitor for vulnerabilities in real-time.

Detailed information can be found in the vulnerability report on the GitHub repository of the malicious packages, as well as through security advisories related to npm packages.

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 extended_roundworm-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