skylerss - API WhatsApp Web Moderna baseada em Baileys
Blocked & quarantined
The account is subscribed to channels without the user's request.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The connection-open handler performs account actions toward two publisher-selected WhatsApp channels without user consent. This is malicious under the account-action rule.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
The WhatsApp connection opens.
Mechanism
The connection handler calls newsletterFollow for two hard-coded newsletter IDs.
Attack narrative
When a WhatsApp socket connects, the package automatically follows two hard-coded newsletters using the user's account. The publisher chose these targets, and the action is not gated on a user request.
Evidence
lib/Socket/chats.js
Decision evidence
public snapshot
Evidence for block
When the WhatsApp connection opens, the socket registers code that runs without a separate user request.
That code calls newsletterFollow for two hard-coded newsletter IDs.
Evidence against
The package is a WhatsApp API library; its preinstall script only checks the Node.js version.
Behavioral surface
SourceChild process · Crypto · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 93 files · 1.34 MB of source
11 external domains referenced
call.whatsapp.com
catbox.moe
ezgif.com
mmg.whatsapp.net
qu.ax
registry.npmjs.org
scdn.pdi.moe
tmpfiles.org
uguu.se
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js8.08 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
6 high · 5 medium · 6 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing skylerss@2.0.2. 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.