Malicious Code Injection in sick_platypus_z3n Package

sick_platypus_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90488: Malicious code in sick_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sick_platypus_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the sick_platypus_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall sick_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 prevent the installation of this package by using npm's package-lock.json file to lock dependencies and avoid fetching potentially malicious packages. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The sick_platypus_z3n package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Tools like Vulert can assist in maintaining the security of your software.

See every vulnerability recorded for sick_platypus_z3n →

Share this vulnerability

FAQ

sick_platypus_z3n is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.

You should immediately remove the sick_platypus_z3n package from your project and monitor your application for any unusual behavior.

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

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 sick_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