Malicious Code Injection in intimate_skink_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-95110: Malicious code in intimate_skink_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The intimate_skink_z3n package 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 aimed at manipulating developer reputation scores through automated publishing of derivative packages. Its functionality is compromised, making it a potential threat to users and developers relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the intimate_skink_z3n package originates from its association with the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputation inflation and potential security risks for developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intimate_skink_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 workaround, you can avoid using the intimate_skink_z3n package altogether. If you have already installed it, you can remove it by executing the following command: npm uninstall intimate_skink_z3n. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The intimate_skink_z3n package poses a significant risk due to its malicious code designed to manipulate npm's ecosystem. It is crucial for developers to be aware of this vulnerability, remove the affected package, and utilize tools like Vulert for ongoing monitoring of their projects.
See every vulnerability recorded for intimate_skink_z3n →
FAQ
The intimate_skink_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should uninstall the intimate_skink_z3n package immediately to mitigate any potential risks.
Currently, there is no patched version available for the intimate_skink_z3n package. It is recommended to remove the package entirely.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
