@dptech-corp/bohr-cli@2.7.19
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe automatic executable download and staging create a real supply-chain exposure, while same-service hash verification and the lack of install-time execution do not establish an attack. Classify as suspicious and warn.
Static reason
One or more suspicious static signals were detected.
Trigger
The package's postinstall hook runs during installation.
Impact
A compromised or misconfigured release service could supply an executable and matching hash that would be staged for later invocation.
Mechanism
The hook retrieves release metadata and hashes from vendor endpoints, downloads companion binaries, verifies their hashes, and stores them under the user's .bohr tools directory. The launcher later runs the platform binary with the caller's arguments.
AI rationale
The automatic executable download and staging create a real supply-chain exposure, while same-service hash verification and the lack of install-time execution do not establish an attack. Classify as suspicious and warn.
Evidence
package.jsonpostinstall.jsrun.js~/.bohr/tools/trisol/current~/.bohr/tools/wenyon/current
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs postinstall.js automatically during installation.
- The postinstall script downloads companion executables and stages them under the user's .bohr tools directory.
- The Trisol manifest and expected hash come from the configured Trisol server.
- The installer checks the downloaded file against that expected hash before making it executable.
- The CLI launcher runs the matching platform binary with the caller's arguments.
Evidence against
- A hash mismatch causes the downloaded file to be deleted and installation to be skipped.
- The inspected JavaScript does not execute the downloaded companion binaries during postinstall.
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"
},
"keywords": [
"bohrium",
"scientific-computing",
"cli",
"paper-search",
"molecular-dyn
Medium
Suspicious Lifecycle Evidence
The package 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.19.
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.19 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.