Malicious Code Injection in square_takin_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96738: Malicious code in square_takin_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 'square_takin_z3n' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood npm with packages that contain malicious scripts designed to manipulate package metadata and inflate developer reputation scores. The presence of such packages poses a significant risk to developers and users relying on the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'square_takin_z3n' originates from its malicious code, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem and may expose users to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall square_takin_z3n
If 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 your dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'square_takin_z3n' package poses a significant threat due to its malicious code that manipulates npm package metadata. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for square_takin_z3n →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to compromised security, loss of trust in the npm ecosystem, and exposure to further malicious activities.
Regularly audit your dependencies using npm audit and utilize tools like Vulert to monitor for vulnerabilities in real-time.
Immediately remove the package from your project and check for any other affected dependencies. Consider updating to a secure version if available.