bungoma@1.0.0
A lightweight, full-featured WhatsApp Web API library for Node.js
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe delayed remote instruction fetch is wired into normal socket initialization and drives authenticated WhatsApp queries for remote-selected identifiers. This is concrete unsolicited account behavior and supports blocking publication.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Creating the messages socket; the callback runs after ninety seconds.
Impact
The remote operator can cause connected accounts to issue queries about chosen newsletter identifiers without an explicit user action.
Mechanism
Fetches a list from a base64-encoded endpoint, then submits a WhatsApp query for each returned identifier while suppressing errors.
Attack narrative
When the package creates its messages socket, it schedules a delayed fetch from an encoded endpoint. It submits authenticated WhatsApp queries for each identifier received, with errors suppressed. This gives the remote endpoint control over unsolicited account activity; there is no caller-request or consent guard around the scheduled task.
AI rationale
The delayed remote instruction fetch is wired into normal socket initialization and drives authenticated WhatsApp queries for remote-selected identifiers. This is concrete unsolicited account behavior and supports blocking publication.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
main.bwmxmd.co.ke
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package presents itself as a WhatsApp Web API library.
- After a delay, the newsletter socket fetches a remote list and sends authenticated WhatsApp queries for each returned identifier without a user call or consent check.
- The active messages socket constructs the newsletter socket during initialization, activating that behavior for socket users.
- Media processing invokes ffmpeg for video thumbnails and uses dynamic import for audio decoding, which are package-aligned utility behaviors.
Evidence against
- The package manifest declares no lifecycle scripts; the identified behavior runs when the WhatsApp socket is initialized.
- The media processing and media download paths concern user-supplied media and retry handling, not credential collection or exfiltration.
Behavioral surface
ChildProcessCryptoEvalFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
9 flagged · loading sourcelib/WABinary/constants.jsView file
603patternName = google_api_key
severity = high
line = 603
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603603patternName = google_api_key
severity = high
line = 603
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603lib/Utils/messages-media.jsView file
•matchType = normalized_sha256
matchedPackage = spencer-baileys@1.0.4
matchedPath = lib/Utils/messages-media.js
matchedIdentity = npm:c3BlbmNlci1iYWlsZXlz:1.0.4
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
6 High4 Medium4 Low
HighHigh Secretlib/WABinary/constants.js
HighBase64 Obscured Urllib/Socket/newsletter.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighPrevious Version Dangerous Deltalib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowEvallib/Utils/messages-media.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bungoma@1.0.0.
See all versions of bungoma for other recorded verdicts.
- Avoid installing bungoma@1.0.0. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.