Malicious Code Vulnerability in stormy_parrot-appteadev Package

stormy_parrot-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109151: Malicious code in stormy_parrot-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 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 stormy_parrot-appteadev package is part of the npm ecosystem, typically used for application 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, contains scripts designed to manipulate package metadata and publish derivative packages, potentially harming developers' reputations and polluting the npm registry.

Vulnerability Detail

The vulnerability in stormy_parrot-appteadev originates from its association with a malicious campaign that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of numerous derivative packages. This behavior can inflate developer reputation scores fraudulently and clutter the npm registry with unwanted packages, posing risks to developers and users relying on 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 stormy_parrot-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 workaround, you can manually remove the stormy_parrot-appteadev package from your project by running the following command: npm uninstall stormy_parrot-appteadev. Additionally, consider using tools like Vulert to monitor your package-lock.json for any vulnerabilities in real-time.

Conclusion

The stormy_parrot-appteadev package contains a serious vulnerability that can lead to the proliferation of malicious packages in the npm registry. It is crucial for developers to remove this package and monitor their projects for any potential threats. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for stormy_parrot-appteadev →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at manipulating package metadata and publishing derivative packages.

The vulnerability can lead to the automatic publication of unwanted packages, potentially harming your project's reputation and cluttering the npm registry.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

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