This report shows the evidence for @bellaxchan/wbails@1.8.3. 2 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20183 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20183 confirms this npm version as malicious.
Advisory
MAL-2026-20183
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @bellaxchan/wbails (npm)
Details
package.json declares a runtime dependency `libsignal` with the value `github:tenka-san/libsignal-node`, an off-registry git source with no commit SHA, no tag, and no integrity check. `npm install @bellaxchan/wbails@1.8.2` resolves this dependency to whatever bytes currently sit on the default branch of that GitHub repository and executes any lifecycle scripts the fetched tree contains. The content of the target repository can be changed at any time by whoever controls it, so install-time behavior for consumers of this package is not fixed by the published tarball. The target repository owner (`tenka-san`) does not match the publishing scope (`@bellaxchan`), so a third-party controls the executed code path.
## Source: ghsa-malware (15e4829620d3d29ef2631e9b538553e381856033d06f0ecd7814c6693586fdec) 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.
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The install hook only enforces a Node.js version requirement. Runtime credentials go to WhatsApp GraphQL endpoints, and the flagged newsletter identifiers are message metadata rather than automatic actions against those channels.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The preinstall hook performs a Node.js version check. Network and message operations occur when the application calls the corresponding client methods.
Impact
No unauthorized credential transfer, install-time data collection, or unrequested account action was found.
Mechanism
GraphQL methods send tokens or configured Wamo authentication to WhatsApp endpoints. Message helpers construct and relay messages to the caller-provided jid.
The versions list below shows the verdict for each recorded version.
Avoid installing @bellaxchan/wbails@1.8.3. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.