Malicious Code Vulnerability in professional_panda-appteadev Package

professional_panda-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107313: Malicious code in professional_panda-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 professional_panda-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within applications but has been compromised, leading to significant security concerns. The vulnerability stems from the package's involvement in generating and publishing derivative packages that can inflate developer reputation scores, which poses risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the professional_panda-appteadev package originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a significant threat to developers and users alike.

How To Fix

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

npm uninstall professional_panda-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, consider removing the professional_panda-appteadev package from your project if it is not essential. You can do this by executing the following command: npm uninstall professional_panda-appteadev. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The professional_panda-appteadev package contains a significant vulnerability due to malicious code that alters package configurations and repopulates the npm registry with compromised packages. It is crucial to take immediate action by updating or removing the package to safeguard your applications.

See every vulnerability recorded for professional_panda-appteadev →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign but has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity.

Yes, you can use Vulert to monitor your application for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality.

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

How To Fix

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

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