Malicious Code Injection in plastic_alligator-appteadev Package

plastic_alligator-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107100: Malicious code in plastic_alligator-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 plastic_alligator-appteadev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of derivative packages. This package is particularly vulnerable due to its association with scripts that automate the generation of harmful variants.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign linked to the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages.

How To Fix

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

npm uninstall plastic_alligator-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 plastic_alligator-appteadev package and replace it with a trusted alternative that provides similar functionality without the associated risks.

Conclusion

The plastic_alligator-appteadev package has been identified as a vector for malicious code that can compromise the integrity of npm packages. It is crucial for developers to remove this package and monitor their applications for vulnerabilities using tools like Vulert to maintain security.

See every vulnerability recorded for plastic_alligator-appteadev →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and repackages itself to inflate developer reputation scores.

You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for any issues.

It is advised to uninstall the plastic_alligator-appteadev package immediately and replace it with a secure alternative.

The main impact is the pollution of the npm registry, which can lead to the proliferation of malicious packages and compromise the security of dependent projects.

Vulert uses your package-lock.json to monitor and alert you in real-time about open-source vulnerabilities, ensuring your software remains secure.

How To Fix

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

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