@fahridevz-baileys/baileys@1.1.0
Baileys milik Fahridevz: support tombol interaktif (native flow) dan AI Rich Response, auto-follow saluran Fahridevz
AI Security Review
scanned 4h ago · by lpm-firewall-aiOn connection, the socket follows a hard-coded publisher-selected newsletter using the user’s WhatsApp account. This is an unrequested account action, so the package is malicious.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The consumer creates a socket and its WhatsApp connection opens.
Impact
The user’s WhatsApp account follows a channel they did not choose.
Mechanism
A connection-update handler resolves the hard-coded invite and calls newsletterFollow; an environment variable can add more invites.
Attack narrative
After a socket connects, the package automatically follows a hard-coded publisher-selected WhatsApp newsletter with the user’s account. The package description mentions auto-following, but the action is still performed by default without a user request.
AI rationale
On connection, the socket follows a hard-coded publisher-selected newsletter using the user’s WhatsApp account. This is an unrequested account action, so the package is malicious.
Evidence
lib/Socket/index.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The socket code includes a hard-coded newsletter invite in its default auto-follow list.
- When the WhatsApp connection opens, the socket looks up each invite and calls newsletterFollow without a user request.
Evidence against
- The package is a WhatsApp automation library, so creating a connected socket is part of its normal use.
- The package description mentions auto-following the publisher’s channel.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
WAProto/index.js
Source & flagged code
8 flaggedlib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600lib/Utils/validate-connection.jsView file
114pull: false,
L115: devicePairingData: {
L116: buildHash: appVersionBuf,
...
L141: const { details, hmac, accountType } = proto.ADVSignedDeviceIdentityHMAC.decode(deviceIdentityNode.content);
L142: let hmacPrefix = Buffer.from([]);
L143: if (accountType !== undefined && accountType === proto.ADVEncryptionType.HOSTED) {
...
L165: ]);
L166: account.deviceSignature = Curve.sign(signedIdentityKey.private, deviceMsg);
L167: const identity = createSignalIdentity(lid, accountSignatureKey);
Findings
5 High5 Medium5 Low
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
HighSecret Patternlib/WABinary/constants.d.ts
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @fahridevz-baileys/baileys@1.1.0.
See all versions of @fahridevz-baileys/baileys for other recorded verdicts.
- Avoid installing @fahridevz-baileys/baileys@1.1.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.