Malicious Code Injection in sweet_owl_z3n: A Threat to npm Packages
Summary
MAL-2025-96909: Malicious code in sweet_owl_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 'sweet_owl_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability originates from the 'sweet_owl_z3n' package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify and republish themselves, removing private flags from package.json, changing version numbers, and generating random names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code for developers who may unknowingly include these packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sweet_owl_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 measure, avoid using the 'sweet_owl_z3n' package and any other packages that may be associated with the tea.xyz token reward campaign. Monitor your package.json and package-lock.json files for any unauthorized changes.
Conclusion
The 'sweet_owl_z3n' package poses a significant security risk due to its malicious behavior of modifying and republishing itself. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for sweet_owl_z3n →
FAQ
The 'sweet_owl_z3n' package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application depends on 'sweet_owl_z3n', it may inadvertently execute malicious code, leading to security breaches or data leaks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the 'sweet_owl_z3n' package immediately using 'npm uninstall sweet_owl_z3n' and review your dependencies for any other malicious packages.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.
