Malicious Code Injection in operational_guanaco_z3n Package
Summary
MAL-2025-95755: Malicious code in operational_guanaco_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 operational_guanaco_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a larger malicious campaign targeting developers by flooding the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish variants that can mislead developers and inflate reputation scores for token rewards.
Vulnerability Detail
This vulnerability originates from the operational_guanaco_z3n package being linked to a malicious campaign that modifies its package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these malicious packages into their applications, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall operational_guanaco_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 operational_guanaco_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The operational_guanaco_z3n package poses a significant risk due to its malicious code that alters package metadata and repackages itself. Developers are advised to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for operational_guanaco_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
If your application uses the operational_guanaco_z3n package, it may be at risk of integrating malicious code that could compromise security and integrity.
You should remove the operational_guanaco_z3n package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
