Malicious Code Injection in sad_parakeet-appteadev: A Threat to npm Users

sad_parakeet-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108325: Malicious code in sad_parakeet-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package sad_parakeet-appteadev is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system for nefarious purposes.

Vulnerability Detail

The vulnerability in sad_parakeet-appteadev 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 and pollute the npm registry with derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing capabilities to distribute harmful scripts.

How To Fix

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

npm uninstall sad_parakeet-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 avoid using the sad_parakeet-appteadev package and monitor your project for any dependencies that might indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The sad_parakeet-appteadev package poses a significant risk due to its malicious code designed to exploit the npm registry. Users are advised to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for sad_parakeet-appteadev →

Share this vulnerability

FAQ

sad_parakeet-appteadev is an npm package associated with a malicious campaign that aims to exploit the npm registry.

The malicious code modifies your package.json file, potentially leading to security risks and pollution of the npm registry.

You should uninstall the sad_parakeet-appteadev package immediately and monitor your project for any related vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

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