Malicious Code Injection in plain_possum-toolteadev Package

plain_possum-toolteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107090: Malicious code in plain_possum-toolteadev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The plain_possum-toolteadev package is part of the npm ecosystem, often utilized in various JavaScript applications for development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs scripts to automatically publish malicious variants of the package. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to security risks and reputational damage.

How To Fix

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

npm uninstall plain_possum-toolteadev

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, consider removing the plain_possum-toolteadev package from your project until a secure version is released. You can do this by executing the following command: npm uninstall plain_possum-toolteadev. Additionally, monitor your package-lock.json file for any dependencies that may introduce vulnerabilities.

Conclusion

The plain_possum-toolteadev 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 and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for plain_possum-toolteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the use of compromised packages, which may introduce security risks and affect the integrity of your application.

You should update the package to the latest version or remove it from your project until a secure version is available.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, 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 plain_possum-toolteadev

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