MAL-2026-20182: Malicious code in @bellaxchan/wabails (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (aed8ba752263403243608bd9df0e0b340e3c0210a1e787f05801e4d7945ebefa) package.json declares the dependency libsignal with the value npm:bellaxchan/libsignal-node, which npm resolves at install time by fetching the current contents of the GitHub repository bellaxchan/libsignal-node. No version tag, branch, or commit SHA is pinned and no integrity hash is checked, so npm install downloads whatever bytes currently sit at that location and runs any lifecycle scripts inside them on the installer's machine. Whoever controls that GitHub account controls the code executed during every install of this package, making the dependency resolution itself the install-time execution vector regardless of the current repository contents.
Source: ghsa-malware (0ff6c20fca2b5b0b16cd035582ce321123ee9b6380dc565e4c544054a0823626) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/@bellaxchan/wabailsfrom your environment.Remove the @bellaxchan/wabails package; removing it may not remove all malicious software resulting from its installation.
- Operational
Immediately rotate all secrets and keys stored on any affected computer, using a different computer.
Event History
Frequently Asked Questions
Who should treat this as an active compromise?
Any computer where @bellaxchan/wabails is installed or running should be considered fully compromised.
What immediate response is recommended?
Rotate all secrets and keys stored on the affected computer immediately, using a different computer to perform the rotation. Remove the package as part of the response.
Is removing the package sufficient to remediate the incident?
No. Because installation may have given an outside entity full control of the computer, removing the package does not guarantee that all resulting malicious software has been removed.