@dptech-corp/bohr-cli@2.7.7
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic lifecycle hook stages remote companion executables in the user's home directory, creating a meaningful supply-chain exposure. Source inspection did not establish a concrete attack, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing the npm package, which runs its postinstall hook.
Impact
A remote publisher-controlled executable is placed for later use; the inspected source does not show it being run by the install hook.
Mechanism
The hook downloads companion tools from the configured Trisol service and installs a binary after comparing its file hash with the hash supplied by the publisher flow.
AI rationale
The automatic lifecycle hook stages remote companion executables in the user's home directory, creating a meaningful supply-chain exposure. Source inspection did not establish a concrete attack, so this warrants a warning rather than a block.
Evidence
package.jsonpostinstall.js~/.bohr/tools/trisol/current~/.bohr/tools/wenyon/current
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs postinstall.js automatically during installation.
- postinstall.js fetches a Trisol manifest from the configured server and installs the companion executable under the user's home directory.
- The downloaded executable is installed after its SHA-256 is checked against a hash obtained through the same publisher-controlled flow.
Evidence against
- The companion tools are installed in a package-specific directory under ~/.bohr/tools.
- The installer verifies the downloaded file hash and handles failures by skipping 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 unpkg8"scripts": {
"postinstall": "node postinstall.js"
},
"keywords": [
"bohrium",
"scientific-computing",
"cli",
"pape
Medium
Suspicious Lifecycle Evidence
package.json runs postinstall.js automatically during installation.
package.jsonView on unpkg · L8run.js#virtual:normalized:round1View file
Findings
3 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltarun.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.7.
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.7 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.