Malicious Code Injection in quickest_platypus_z3n Package

quickest_platypus_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107656: Malicious code in quickest_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 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 quickest_platypus_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with packages that manipulate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with altered metadata, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the quickest_platypus_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, often themed around Indonesian culture. The primary risk is that it can lead to the proliferation of untrustworthy packages in the npm registry, which can compromise the integrity of applications relying on these packages. The malicious payload is part of a broader scheme to inflate developer reputation scores for token rewards, making it a significant concern for developers and users alike.

How To Fix

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

npm uninstall quickest_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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The quickest_platypus_z3n package contains malicious code that can compromise the security of applications using it. It is crucial to uninstall this package and monitor your project for vulnerabilities. Utilizing tools like Vulert can help ensure your application remains secure against such threats.

See every vulnerability recorded for quickest_platypus_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate developer reputation scores.

The malicious code can lead to the creation of untrustworthy packages, potentially compromising your application's integrity and security.

The best way to fix the vulnerability is to uninstall the quickest_platypus_z3n package and replace it with a secure alternative.

You can use Vulert, which allows you to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

If you have used this package, uninstall it immediately and check your project for any dependencies that may have been affected.

How To Fix

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

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