Malicious Code Injection in obvious_lynx_z3n Package - npm Vulnerability
Summary
MAL-2025-88967: Malicious code in obvious_lynx_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 obvious_lynx_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a malicious campaign that floods npm with packages designed to inflate developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that automatically publish derivative packages with altered names and metadata, compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers relying on the integrity of the ecosystem. The malicious payload can compromise the security of applications using this package, leading to unintended consequences such as dependency confusion and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall obvious_lynx_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 obvious_lynx_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to check your package-lock.json for vulnerabilities: npm audit.
Conclusion
The obvious_lynx_z3n package poses significant risks due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for obvious_lynx_z3n →
FAQ
obvious_lynx_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially causing dependency confusion and security risks for applications relying on this package.
You should uninstall the package immediately and check for any dependencies that may rely on it. Consider using alternative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
