Malicious Code Injection in fluttering_pig-appteadev: A Threat to npm Packages

fluttering_pig-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102834: Malicious code in fluttering_pig-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

fluttering_pig-appteadev is an npm package that is part of a larger ecosystem of packages related to the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to manipulate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm registry.

Vulnerability Detail

The vulnerability in fluttering_pig-appteadev stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry and potentially compromising other packages. The origin of this vulnerability is linked to a campaign that exploits npm's publishing mechanisms to inflate reputation scores fraudulently.

How To Fix

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

npm uninstall fluttering_pig-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 fluttering_pig-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The fluttering_pig-appteadev package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to remove this package from your projects and utilize monitoring tools like Vulert to safeguard against future vulnerabilities.

See every vulnerability recorded for fluttering_pig-appteadev →

Share this vulnerability

FAQ

fluttering_pig-appteadev is an npm package involved in a token reward campaign that automates the publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

You should uninstall the package immediately using the command: npm uninstall fluttering_pig-appteadev.

Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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