ipungg-baileys@1.0.2
WhatsApp Web API Library - Ipung Baileys with Auto Channel Follow
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection confirms an automatic account action: the normal socket constructor follows a fixed publisher-selected newsletter. This is concrete unauthorized account mutation, so publication should be blocked.
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
Calling the package’s socket constructor starts the follow routine; it also retries after the connection opens.
Impact
The authenticated account is subscribed to a publisher-selected channel without the caller choosing that target.
Mechanism
The routine sends a follow query for a hard-coded newsletter ID through the WhatsApp network.
Attack narrative
The public socket constructor reaches the newsletter socket, which starts a background routine that follows a fixed channel when the socket is created and again after connection opens. The routine retries if needed. This changes the authenticated account’s subscriptions without the caller selecting the channel.
AI rationale
Source inspection confirms an automatic account action: the normal socket constructor follows a fixed publisher-selected newsletter. This is concrete unauthorized account mutation, so publication should be blocked.
Evidence
package.jsonlib/index.jslib/Socket/index.jslib/Socket/registration.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/newsletter.jslib/Types/Newsletter.jslib/WABinary/jid-utils.js
Network endpoints1
s.whatsapp.net
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The socket sends a follow action for a fixed newsletter ID through the WhatsApp network query path.
- The follow runs automatically when the newsletter socket is created, with startup and connection timers and retries.
- The package’s public socket entrypoint reaches the newsletter socket through the normal constructor chain.
Evidence against
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
GitDependency
Oversized source lightweight scan
WAProto/index.js4.60 MB file, sampled 256 KB
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgWAProto/index.jsView file
•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
WAProto/index.jsView on unpkg•path = WAProto/index.js
kind = oversized_source_file
sizeBytes = 4824821
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgFindings
5 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to ipungg-baileys@1.0.2.
See all versions of ipungg-baileys for other recorded verdicts.
- Avoid installing ipungg-baileys@1.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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.