Critical Security Breach in @actbase/native: Malicious Code Injection Detected
Summary
MAL-2025-191178: Malicious code in @actbase/native (npm). Affects @actbase/native versions 0.1.32. 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 @actbase/native package is a Node.js library designed for native application development. It provides various functionalities that facilitate the integration of native features into JavaScript applications. However, this package has been compromised, making it susceptible to severe security threats, including unauthorized access to sensitive user data.
Vulnerability Detail
The vulnerability stems from a malicious code injection attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from users and publish them to GitHub. It can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Additionally, the worm has the potential to destroy the user's home directory, leading to significant data loss and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @actbase/nativeIf 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, consider removing the @actbase/native package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall @actbase/native'. Additionally, monitor your application for any unauthorized access or unusual activity.
Conclusion
The @actbase/native package has been compromised by a malicious worm that poses significant security risks. Users are advised to update their packages, monitor their applications for unusual activity, and consider using tools like Vulert for ongoing vulnerability management.
See every vulnerability recorded for @actbase/native →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials and can propagate itself to other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you suspect that your application has been compromised, immediately remove the affected package and change any exposed credentials.
Currently, there is no specific patched version mentioned, but it is essential to keep an eye on updates from the package maintainers.
The worm propagates by infecting other NPM packages owned by the user and establishing persistence through GitHub actions.
