Malicious Code Injection in binding_skink_z3n: A Threat to npm Packages
Summary
MAL-2025-93385: Malicious code in binding_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
Background
The package 'binding_skink_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores for token rewards. The package's primary function is compromised due to the presence of these malicious elements.
Vulnerability Detail
The vulnerability in 'binding_skink_z3n' originates from its association with a malicious campaign that employs autopublish scripts. These scripts modify the package.json file to remove private flags, alter version numbers, and generate 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 binding_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 temporary workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'binding_skink_z3n' in its dependencies. You can also use the following command to uninstall it: npm uninstall binding_skink_z3n.
Conclusion
The 'binding_skink_z3n' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for binding_skink_z3n →
FAQ
'binding_skink_z3n' is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for token rewards.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.
You should immediately uninstall 'binding_skink_z3n' and check your project for any other potentially compromised packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
