@dptech-corp/bohr-cli@2.7.8
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe lifecycle hook creates a real automatic remote executable installation capability, so this warrants a warning as a staged payload carrier. The inspected behavior is consistent with companion-tool setup, verifies file hashes, and shows no concrete attack behavior or consumer-project mutation.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm installation invokes the package's postinstall hook.
Impact
The release services control which companion tool versions are offered; successfully installed tools are available on the user's machine but are not executed by this hook.
Mechanism
The hook requests release metadata or a manifest, downloads selected executables, verifies the downloaded file hash, then marks the file executable and installs it under ~/.bohr/tools.
AI rationale
The lifecycle hook creates a real automatic remote executable installation capability, so this warrants a warning as a staged payload carrier. The inspected behavior is consistent with companion-tool setup, verifies file hashes, and shows no concrete attack behavior or consumer-project mutation.
Evidence
package.jsonpostinstall.js~/.bohr/tools/wenyon/current~/.bohr/tools/trisol/current
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package automatically runs postinstall.js during installation.
- The hook downloads companion executables into the user's ~/.bohr/tools directories and marks them executable after checking their hashes.
- Trisol release channel and version are obtained from a remote manifest; Wenyon release metadata supplies its download URL and hash.
- The launcher locates and starts the platform-specific Bohr binary.
Evidence against
- The hook installs companions under product-specific directories rather than changing consumer project files or agent control surfaces.
- The downloaded executable bytes are checked against a required SHA-256 value before installation.
- The inspected source contains no credential collection or transmission behavior.
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",
"scientif
Medium
Suspicious Lifecycle Evidence
The package automatically runs postinstall.js 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.8.
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.8 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.