Malicious Code Injection in personal_platypus_z3n Package

personal_platypus_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107046: Malicious code in personal_platypus_z3n (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 personal_platypus_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the personal_platypus_z3n package stems from its inclusion in a malicious campaign that deploys scripts designed to automatically generate and publish derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, which leads to pollution of the npm registry and potential security risks for users who unknowingly install these variants.

How To Fix

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

npm uninstall personal_platypus_z3n

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 personal_platypus_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your npm registry is set to a trusted source to minimize the risk of installing malicious packages.

Conclusion

The personal_platypus_z3n package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to uninstall this package and monitor your projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software by providing alerts for open-source vulnerabilities.

See every vulnerability recorded for personal_platypus_z3n →

Share this vulnerability

FAQ

The personal_platypus_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

If your application uses the personal_platypus_z3n package, it may be at risk of installing malicious derivatives that can compromise security and integrity.

You should immediately uninstall the personal_platypus_z3n package and check your project for any unauthorized changes.

Yes, Vulert can monitor your project for open-source vulnerabilities using just the package-lock.json file, providing real-time alerts.

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

How To Fix

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

npm uninstall personal_platypus_z3n

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