Malicious Code Injection in final_octopus_z3n Package
Summary
MAL-2025-94509: Malicious code in final_octopus_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 final_octopus_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that can manipulate project files and degrade the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the final_octopus_z3n package stems from its inclusion in a malicious campaign that employs scripts to automatically publish derivative packages with altered metadata. This includes removing private flags from package.json files, changing version numbers, and generating random package names. The malicious payload can lead to the pollution of the npm registry, potentially affecting developers' reputation scores and compromising the security of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall final_octopus_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 avoid using the final_octopus_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The final_octopus_z3n package poses a significant risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software projects.
See every vulnerability recorded for final_octopus_z3n →
FAQ
The final_octopus_z3n package is an npm package that has been compromised to include malicious code as part of a token reward campaign.
The malicious code can modify your package.json file, remove private flags, and publish altered versions of your package, potentially harming your project's integrity.
You should uninstall the final_octopus_z3n package immediately using 'npm uninstall final_octopus_z3n' and check for any other affected packages.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or install additional software.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.