registry / lordceaser-baileys / 2.0.22
lordceaser-baileys@2.0.22
Static Scan Results
scanned 2mo ago · by rust-scannerStatic analysis completed at 65.0% confidence. No malicious behavior was detected; 11 low-signal pattern(s) were surfaced and cleared.
Static reason
No blocking static signals were detected.
Decision evidence
public snapshotBehavioral surface
ChildProcessCryptoDynamicRequireEvalFilesystemNetworkWebSocket
HighEntropyStringsMinifiedUrlStrings
Oversized source lightweight scan
WAProto/WAProto/index.js7.85 MB file, sampled 256 KB
ChildProcess
WAProto/WAProto/index.ts.ts2.27 MB file, sampled 256 KB
WAProto/index.js7.85 MB file, sampled 256 KB
ChildProcess
WAProto/index.ts.ts2.27 MB file, sampled 256 KB
Source & flagged code
6 flaggedlib/Utils/messages-media.jsView file
247try {
L248: const { default: decoder } = await eval('import(\'audio-decode\')')
L249: let audioData
Low
Eval
Package source references a known benign dynamic code generation pattern.
lib/Utils/messages-media.jsView on unpkg · L247index.jsView file
1module.exports = require('./lib/index.js');
Medium
lib/Utils/crypto.jsView file
42return {
L43: private: Buffer.from(privKey),
L44: public: Buffer.from(pubKey.slice(1))
Findings
1 High5 Medium5 Low
HighSemantic Analysis LimitedWAProto/index.js
MediumDynamic Requireindex.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowEvallib/Utils/messages-media.js
LowWeak Cryptolib/Utils/crypto.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to lordceaser-baileys@2.0.22.
See all versions of lordceaser-baileys for other recorded verdicts.
- Review the evidence and your use of lordceaser-baileys@2.0.22 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.