Malicious Code Injection in eligible_sparrow-appteadev: npm Package Vulnerability

eligible_sparrow-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102047: Malicious code in eligible_sparrow-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 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 eligible_sparrow-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

This vulnerability originates from the package being part of a malicious campaign that deploys scripts designed to automatically generate and publish derivative packages with randomized names. These scripts, such as auto.js and autopublish.js, modify the package.json file to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially affecting developers' reputations and the integrity of the ecosystem.

How To Fix

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

npm uninstall eligible_sparrow-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 prevent the installation of this specific package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check for open-source vulnerabilities in real-time without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The eligible_sparrow-appteadev package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package and to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for eligible_sparrow-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

The vulnerability can lead to the pollution of the npm registry and may affect your project's integrity and developer reputation.

If no patched version is available, consider removing the package from your project to mitigate the risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

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