Malicious Code Injection in gerardo-teadev Package - npm Vulnerability

gerardo-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103113: Malicious code in gerardo-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gerardo-teadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the gerardo-teadev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic publication of numerous derivative packages. This behavior not only pollutes the npm registry but can also inflate developer reputation scores fraudulently, posing a significant risk to the integrity of the npm ecosystem.

How To Fix

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

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

Conclusion

The gerardo-teadev package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential exploitation.

See every vulnerability recorded for gerardo-teadev →

Share this vulnerability

FAQ

The gerardo-teadev package is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The vulnerability allows the package to modify package.json files, remove private flags, and publish numerous derivative packages, thereby polluting the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.

If an immediate update is not possible, you should uninstall the gerardo-teadev package to mitigate the risk of malicious code execution.

Detailed information about this vulnerability can be found in the official npm registry and security advisories related to the gerardo-teadev package.

How To Fix

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

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