sixbails
This report shows the evidence for sixbails@1.1.1. 11 of 12 known versions are blocked or flagged. The newest version, 1.1.2, is flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-11088 confirms this npm version as malicious.
Advisory
MAL-2026-11088
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in sixbails (npm)
Details
sixbails is a WhatsApp Web library (Baileys-family fork). On every socket creation — the package's primary documented API — a 5-second timer fires `newsletterWMexQuery("120363425547320365@newsletter", QueryIds.FOLLOW)` from lib/Socket/newsletter.js (lines 101-105), causing the consumer's authenticated WhatsApp account to silently follow a hardcoded newsletter channel owned by the author. The behavior is disclosed in the README ("Has 1 newsletter follow, only the developer's WhatsApp channel"), so it is disclosed self-promotion rather than covert exfiltration, and no installer-machine secrets, environment variables, or filesystem contents are sent anywhere. The blast radius is confined to the consumer's WhatsApp account state (one extra channel subscription). Separately, package.json line 48 pins `libsignal` to `github:tenka-san/libsignal-node` with no commit SHA, branch, or tag — whoever controls that repo's default branch can change cryptographic primitives in future installs (this mirrors upstream Baileys's unpinned libsignal fork pattern). The declared preinstall hook (`node./engine-requirements.js`) is a benign Node>=20 version check with no network or filesystem side effects. Routing to human review so a maintainer can decide whether the disclosed-but-still-hardcoded WhatsApp follow + unpinned third-party crypto fork warrant a public advisory.
## Source: ghsa-malware (39404fc7b16b66b76bed0e8794563ad0a40a0f16dafd81fbe68f35e2c5bc9678) 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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to sixbails@1.1.1.
The same advisory and Firewall decision cover 6 recorded versions
1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.7, 1.1.1
The versions list below shows the verdict for each recorded version.
- Avoid installing sixbails@1.1.1. 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.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.