registry / Credential exfiltration / cr-bot-common
cr-bot-common
Common utilities for CryptoBot - TON wallet integration
This report shows the evidence for cr-bot-common@1.0.0, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is concrete, automatic install-time credential and data exfiltration to an attacker-controlled endpoint. The lifecycle hooks make the behavior execute without an explicit user command.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation of the package
Impact
Disclosure of environment secrets, configuration contents, private keys, and host metadata.
Mechanism
install-time credential harvesting and HTTPS exfiltration
Attack narrative
On npm installation, package.json runs preinstall.js and postinstall.js. The scripts collect environment files, sensitive environment variables, project configuration, key-like files, and host metadata. They serialize the data and POST it to attacker.com, suppressing errors to avoid visible failures. The postinstall hook additionally scans common system directories for credential-like files. A bundled helper explicitly labels publication as a dependency-confusion attack and references C2 callbacks.
AI rationale
This is concrete, automatic install-time credential and data exfiltration to an attacker-controlled endpoint. The lifecycle hooks make the behavior execute without an explicit user command.
Evidence
package.jsonpreinstall.jspostinstall.jspublish.sh.env.env.local.env.production../.env../../.envconfig.jswallet.jskeys.js
Network endpoints2
attacker.com/collectattacker.com/exfiltrate
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Installation automatically runs both collection scripts.
- The preinstall hook reads project and parent environment files, configuration files, and likely key files from the home directory.
- The hooks collect sensitive environment variables and send a JSON payload to attacker.com over HTTPS.
- The postinstall hook also searches common system locations for private keys and credentials.
- The shipped publishing helper explicitly describes a dependency-confusion attack and C2 callbacks.
- The postinstall code configures attacker.com as its C2 exfiltration endpoint.
- The publishing helper explicitly labels its activity a dependency-confusion attack.
Evidence against
- index.js only exports ordinary address, amount, retry, and conversion helpers.
- No legitimate runtime feature requires the install-time collection or outbound requests.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"scripts": {
"postinstall": "node postinstall.js",
"preinstall": "node preinstall.js"
},
High
Ai Review Evidence
Installation automatically runs both collection scripts.
package.jsonView on unpkg · L6•scripts.preinstall = node preinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Findings
4 High6 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighAi Review Evidencepackage.json
HighAi Review Evidencepreinstall.js
HighSuspicious Lifecycle Evidencepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperpublish.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to cr-bot-common@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing cr-bot-common@1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.