Malicious Code Injection in static_platypus_z3n: A Threat to npm Packages
Summary
MAL-2025-96753: Malicious code in static_platypus_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'static_platypus_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating numerous derivative packages with randomized names. The intent behind this is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability in 'static_platypus_z3n' originates from its association with a malicious campaign that includes scripts designed to autopublish variants of the package. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to pollution of the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_platypus_z3nIf 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 'static_platypus_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'static_platypus_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for static_platypus_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json and repackages itself, leading to pollution of the npm registry.
You can check your package.json file or run 'npm list static_platypus_z3n' in your terminal to see if it is included in your dependencies.
You should uninstall the package immediately using 'npm uninstall static_platypus_z3n' and look for secure alternatives.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.
