Malicious Code Injection in poor_frog-appteadev Package

poor_frog-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107138: Malicious code in poor_frog-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The poor_frog-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate development processes but has recently been implicated in a malicious campaign. The package has been associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that aim to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in the poor_frog-appteadev package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is executed through autopublish scripts that continuously republish variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these malicious packages into their applications, leading to compromised systems and reputational damage.

How To Fix

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

npm uninstall poor_frog-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 remove the poor_frog-appteadev package from your project by executing the command: npm uninstall poor_frog-appteadev. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.

Conclusion

The poor_frog-appteadev package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects.

See every vulnerability recorded for poor_frog-appteadev →

Share this vulnerability

FAQ

The poor_frog-appteadev package is an npm package used in JavaScript development, but it has been compromised by malicious actors.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

You should immediately update or uninstall the package to mitigate any risks associated with the vulnerability.

Yes, tools like Vulert can monitor your package-lock.json for vulnerabilities in real-time without requiring code access.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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