Malicious Code Injection in awake_swallow_requirement Package
Summary
MAL-2025-93324: Malicious code in awake_swallow_requirement (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 awake_swallow_requirement package is part of the npm ecosystem, often utilized in JavaScript projects. It is designed to facilitate certain functionalities within applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing system, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, compromising the integrity of the ecosystem and potentially exposing users to further security threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall awake_swallow_requirementIf 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 remove the awake_swallow_requirement package from your project by executing: npm uninstall awake_swallow_requirement. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The awake_swallow_requirement package has been identified as containing malicious code that poses significant risks to developers and users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for awake_swallow_requirement →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without needing to sign up.
If immediate updates are not feasible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the vulnerability poses risks of unauthorized package modifications and potential security breaches.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
