charape@1.0.3
Enterprise-grade WhatsApp Web Baileys library and multi-bot runner supervisor with session crash guard.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe automatic postinstall hook performs unconsented writes into consumer dependency paths and can replace existing packages, while also changing project-wide npm configuration. This concrete install-time destructive behavior warrants blocking publication.
Static reason
One or more suspicious static signals were detected.
Trigger
Automatic package installation, when the package is installed under node_modules.
Impact
Existing Baileys packages can be replaced by proxies to charape, changing which code consumer imports and altering npm dependency resolution behavior.
Mechanism
The hook targets three Baileys paths, creates a target directory only if missing, then writes proxy package and entrypoint files unconditionally. It also sets legacy-peer-deps in the consumer project's .npmrc.
Attack narrative
On installation, the postinstall hook writes proxy manifests and entrypoints into the consumer's Baileys package paths without preserving existing files. It also changes the consumer's npm configuration. The compatibility-bridge comment indicates a possible intended use, but does not guard or limit the overwrite.
AI rationale
The automatic postinstall hook performs unconsented writes into consumer dependency paths and can replace existing packages, while also changing project-wide npm configuration. This concrete install-time destructive behavior warrants blocking publication.
Evidence
package.jsonscripts/postinstall.js
Decision evidence
public snapshotAI called this Malicious at 90.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs scripts/postinstall.js automatically after installation.
- The hook targets three Baileys package paths inside the consumer's node_modules and writes proxy files there even when those targets already exist.
- The hook also creates or changes the consumer project's .npmrc to enable legacy-peer-deps.
Evidence against
- The source describes the Baileys paths as compatibility bridges, which may explain the intended purpose, but the writes still replace files at existing package paths.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node ./scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkglib/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 · L600Findings
6 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighChild Processbin/charape.js
HighCommand Output Exfiltrationlib/Utils/messages-media.js
HighSemantic Analysis LimitedWAProto/index.cjs
HighSecret Patternlib/WABinary/constants.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source Filelib/index.cjs
MediumStructural Risk Force Deep Review
LowScripts Present
Low
Affected versions and remediation
This report applies to charape@1.0.3.
See all versions of charape for other recorded verdicts.
- Avoid installing charape@1.0.3. 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.