registry / @dptech-corp/bohr-cli / 2.7.2
@dptech-corp/bohr-cli@2.7.2
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe postinstall hook performs automatic, package-owned companion executable setup, so the unresolved release trust warrants a warning. The inspected source shows hash checks and package-aligned tool paths, but no concrete malicious action.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing the npm package runs its postinstall hook.
Impact
A compromised or untrusted release service or metadata response could supply executable companion tools that are installed for later use.
Mechanism
The hook retrieves release information and binaries from the configured services, checks downloaded bytes against service-provided SHA-256 values, then installs accepted files as executables.
AI rationale
The postinstall hook performs automatic, package-owned companion executable setup, so the unresolved release trust warrants a warning. The inspected source shows hash checks and package-aligned tool paths, but no concrete malicious action.
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 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package postinstall hook automatically runs `postinstall.js`.
- The hook downloads companion executables from `wenyon.dp.tech` and `trisol.dp.tech` into the user's `~/.bohr/tools` directory.
- The downloaded files are installed as executables after their hashes are checked against values fetched from the services.
- The Wenyon download URL is supplied by release metadata fetched during postinstall.
Evidence against
- The manifest identifies the package as a Bohrium scientific computing CLI and the launcher resolves a platform-specific package binary.
- The installer refuses files with missing or invalid SHA-256 values and skips files whose computed hash does not match.
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",
Medium
Suspicious Lifecycle Evidence
The package postinstall hook automatically runs `postinstall.js`.
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.2.
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.2 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.