@dptech-corp/bohr-cli@2.7.23
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe install hook automatically downloads and stages executable companion tools, with integrity checks based on the release services' own metadata. This is a real payload-staging risk, but the inspected source does not establish a malicious payload or execution during installation.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the npm package triggers its postinstall script.
Impact
A compromised or misleading release service could cause an unexpected executable to be staged for later use; the inspected hook does not launch these companion binaries during installation.
Mechanism
The hook retrieves release metadata, downloads the named binaries, checks the downloaded bytes against the supplied hashes, and stores them as executable files.
AI rationale
The install hook automatically downloads and stages executable companion tools, with integrity checks based on the release services' own metadata. This is a real payload-staging risk, but the inspected source does not establish a malicious payload or execution during installation.
Evidence
package.jsonpostinstall.js~/.bohr/tools/wenyon/current~/.bohr/tools/trisol
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs postinstall.js automatically during installation.
- The hook fetches companion-tool release metadata from the Trisol and Wenyon services.
- The Wenyon download URL and expected hash both come from release metadata.
- The hook downloads each binary, checks its SHA-256, then marks it executable and stores it.
- Companion tools are stored under the user's .bohr tools directory.
Evidence against
- The hook checks downloaded bytes against a SHA-256 supplied by the release service before storing the executable.
- The inspected postinstall flow downloads and stores companion binaries; it does not show them being launched during installation.
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 unpkg9"postinstall": "node postinstall.js"
},
Medium
Suspicious Lifecycle Evidence
The manifest runs postinstall.js automatically during installation.
package.jsonView on unpkg · L9run.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
MediumSuspicious Lifecycle Evidencepostinstall.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.23.
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.23 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.