pikachu-baileys@7.0.0
Custom Baileys milik Ndraa (fork dari Baileys), auto-follow saluran Pikachu MD
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe package performs a default account action toward a publisher-selected newsletter when the socket connects. The description discloses auto-follow, but this remains an unrequested account action under the review rules.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The WhatsApp connection opens after the consumer creates the socket.
Impact
The linked WhatsApp account joins a newsletter selected by the package publisher.
Mechanism
The connection handler resolves the hard-coded invite and calls newsletterFollow without requiring a separate user request.
Attack narrative
After a socket connects, the package automatically resolves a hard-coded newsletter invite and follows that newsletter with the user's connected WhatsApp account. The package description discloses the auto-follow feature, but the follow still occurs by default toward a publisher-selected target.
AI rationale
The package performs a default account action toward a publisher-selected newsletter when the socket connects. The description discloses auto-follow, but this remains an unrequested account action under the review rules.
Evidence
lib/Socket/index.jslib/index.js
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- A hard-coded newsletter invite is included in the default auto-follow list.
- When the WhatsApp connection opens, the socket processes the auto-follow list.
- The socket looks up each invite and calls newsletterFollow for its resolved ID.
- The package entry point imports and exports the socket factory containing this behavior.
Evidence against
- The package description discloses that this fork auto-follows the Pikachu MD channel.
- The manifest has no install, preinstall, or postinstall lifecycle script.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
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 pikachu-baileys@7.0.0.
See all versions of pikachu-baileys for other recorded verdicts.
- Avoid installing pikachu-baileys@7.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.