@dptech-corp/bohr-cli@2.7.20
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe hook automatically downloads and stages executable companion tools, creating a staged payload carrier risk. Its Bohr-specific destinations and hash checks are mitigating facts, but do not remove the warning for automatic executable staging.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the npm package runs its postinstall hook.
Impact
The install adds executable companion tools that may be run later; no automatic execution of those tools is established by the inspected hook.
Mechanism
The hook fetches release metadata and binaries, checks each downloaded file against an expected SHA-256 value, then marks it executable and installs it under the user's Bohr tools directory.
AI rationale
The hook automatically downloads and stages executable companion tools, creating a staged payload carrier risk. Its Bohr-specific destinations and hash checks are mitigating facts, but do not remove the warning for automatic executable staging.
Evidence
package.jsonpostinstall.js~/.bohr/tools/trisol/current~/.bohr/tools/wenyon/current
Network endpoints2
trisol.dp.techwenyon.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs postinstall.js automatically after installation.
- The hook fetches companion release information and passes release URLs to its installer.
- The installer downloads executable files, compares their SHA-256 values with expected values, then makes them executable and installs them.
- The companion tools are placed in Bohr-specific directories under the user's home folder; the source identifies Bohr vendor endpoints.
Evidence against
- The source checks downloaded file hashes before installation, and the identified default endpoints are Bohr vendor domains. This reduces risk but does not independently authenticate the server-provided hashes.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg8"scripts": {
"postinstall": "node postinstall.js"
},
"keywords": [
Medium
Suspicious Lifecycle Evidence
The manifest runs postinstall.js automatically after installation.
package.jsonView on unpkg · L8run.js#virtual:normalized:round1View file
Findings
2 High6 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidencepostinstall.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.20.
See all versions of @dptech-corp/bohr-cli for other recorded verdicts.
- Review the evidence and your use of @dptech-corp/bohr-cli@2.7.20 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.