Malicious Code Injection in guerra-teadev Package - npm Vulnerability

guerra-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103425: Malicious code in guerra-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 guerra-teadev package is part of the npm ecosystem, primarily used for JavaScript development. It is designed to facilitate various development tasks but has been compromised, leading to significant security concerns. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages in the npm registry.

Vulnerability Detail

The vulnerability in the guerra-teadev package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, resulting in a polluted npm registry. The malicious payload can lead to unauthorized access, data breaches, and the potential for further exploitation of dependent applications.

How To Fix

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

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

Conclusion

The guerra-teadev package has been identified as containing malicious code that poses significant security risks. It is essential to update or remove this package to protect your application. Utilizing tools like Vulert can help you monitor for such vulnerabilities in real-time.

See every vulnerability recorded for guerra-teadev →

Share this vulnerability

FAQ

guerra-teadev is an npm package used in JavaScript development, but it has been compromised to include malicious code.

The malicious code modifies your package.json file and can lead to unauthorized access and data breaches.

Yes, you can use Vulert to monitor and alert for vulnerabilities in your application without any installation. Visit Vulert Scanner to check your application.

You can temporarily uninstall the guerra-teadev package to mitigate the risk until a secure version is available.

You can reach out to Amazon Inspector at actran@amazon.com for further details regarding this vulnerability.

How To Fix

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

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