Critical Malicious Code Vulnerability in @afetcan/storage Package
Summary
MAL-2025-191180: Malicious code in @afetcan/storage (npm). Affects @afetcan/storage versions 0.0.27. 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 @afetcan/storage package is an npm library designed for efficient storage management in JavaScript applications. It provides functionalities for handling data storage and retrieval, making it a popular choice among developers. However, this package has recently been compromised, exposing users to significant security risks.
Vulnerability Detail
The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, there is a risk that the worm may destroy the user's home directory, leading to potential data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @afetcan/storageIf 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, users should avoid using the affected version (0.0.27) of the @afetcan/storage package. Instead, consider using an alternative package for storage management until a secure version is released.
Conclusion
The @afetcan/storage package has been compromised by a malicious worm, posing serious security risks to users. It is essential to update the package to a secure version and monitor your applications for any signs of compromise. Utilizing tools like Vulert can aid in maintaining the security of your open-source dependencies.
See every vulnerability recorded for @afetcan/storage →
FAQ
The vulnerability can lead to unauthorized access to sensitive information, including tokens and credentials, and may result in data loss.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If immediate updates are not possible, consider using alternative packages or implementing additional security measures to protect sensitive data.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.
Signs of compromise may include unexpected behavior, unauthorized access attempts, or unusual activity in your GitHub repositories.
