Malicious Code Injection in slippery_swift_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96631: Malicious code in slippery_swift_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 'slippery_swift_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'slippery_swift_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall slippery_swift_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 'slippery_swift_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'slippery_swift_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for slippery_swift_z3n →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
Using this package can compromise your project's integrity and expose it to further vulnerabilities, as it modifies critical files and republish variants to the npm registry.
You should remove the 'slippery_swift_z3n' package from your project immediately and monitor for any updates or patches.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
