Malicious Code Injection in short_opossum_0xrequest Package
Summary
MAL-2025-108637: Malicious code in short_opossum_0xrequest (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 short_opossum_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been implicated in a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package has been identified as containing harmful scripts that alter its own metadata and republish itself under random names, contributing to registry pollution.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the short_opossum_0xrequest package, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is part of a broader scheme to exploit the npm registry by continuously republishing variants of the package, thereby compromising the integrity of the ecosystem and potentially affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall short_opossum_0xrequestIf 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, you can avoid using the short_opossum_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.
Conclusion
The short_opossum_0xrequest package poses a significant risk due to its malicious code that alters package metadata and contributes to npm registry pollution. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for short_opossum_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The malicious code modifies your package.json file, removes private flags, and republishes the package under random names, which can lead to registry pollution and potential security risks.
You should uninstall the short_opossum_0xrequest package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and avoid using unverified packages from the npm registry.
