Malicious Code Injection in static_skink_z3n Package
Summary
MAL-2025-96755: Malicious code in static_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 static_skink_z3n package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the static_skink_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially leading to security risks for developers who inadvertently use these compromised packages. The malicious payload can affect the integrity of the npm ecosystem and compromise the security of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_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 manually edit your package.json file to remove any references to static_skink_z3n and its dependencies. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.
Conclusion
The static_skink_z3n package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for static_skink_z3n →
FAQ
static_skink_z3n is an npm package that has been associated with a token reward campaign and has been found to contain malicious code.
The malicious code modifies your package.json file and can lead to the installation of compromised packages, potentially affecting your application's security.
You should remove the static_skink_z3n package from your project immediately and check for any other vulnerabilities using npm audit.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
