Critical Malicious Code Vulnerability in @alexcolls/nuxt-socket.io Package
Summary
MAL-2025-191185: Malicious code in @alexcolls/nuxt-socket.io (npm). Affects @alexcolls/nuxt-socket.io versions 0.0.7 – 0.0.8. 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 @alexcolls/nuxt-socket.io package is a Node.js library designed to facilitate real-time communication in Nuxt.js applications using WebSockets. It provides developers with an easy way to integrate socket.io functionality into their projects, enhancing user experience through live updates and interactions. However, this package has recently been compromised, making it susceptible to severe security threats.
Vulnerability Detail
The vulnerability stems from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing sensitive tokens and credentials from users and publishing them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The worm poses a significant risk as it may also delete 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 @alexcolls/nuxt-socket.ioIf 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
If immediate updating is not possible, consider removing the package from your project until a secure version is available. You can do this by running: npm uninstall @alexcolls/nuxt-socket.io. Additionally, monitor your environment for any unauthorized access or changes.
Conclusion
The @alexcolls/nuxt-socket.io package has been compromised, leading to significant security vulnerabilities that can affect users' sensitive information and system integrity. It is essential to take immediate action by updating or removing the package to protect your applications.
See every vulnerability recorded for @alexcolls/nuxt-socket.io →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials and can also delete files from the user's home directory.
You can check your package-lock.json file for the presence of the @alexcolls/nuxt-socket.io package and its versions. For a more automated approach, use Vulert to monitor your dependencies.
Immediately update the package to the latest version or remove it from your project to mitigate risks.
Yes, Vulert can monitor your project for vulnerabilities in real-time using just your package-lock.json file, providing alerts for any open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
