registry / @dptech-corp/bohr-cli / 2.6.89
@dptech-corp/bohr-cli@2.6.89
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic remote binary installer creates a meaningful supply-chain risk, but source confines writes to its own tool directory and shows no concrete malicious behavior. The package warrants a warning rather than a publication block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall after installing @dptech-corp/bohr-cli
Impact
A compromised or unverified configured service can place a future-executable binary in the Bohr tool directory.
Mechanism
Automatic remote companion-binary download and local installation
AI rationale
The automatic remote binary installer creates a meaningful supply-chain risk, but source confines writes to its own tool directory and shows no concrete malicious behavior. The package warrants a warning rather than a publication block.
Evidence
package.jsonpostinstall.js~/.bohr/tools/wenyon/current/wenyon-cli~/.bohr/tools/wenyon/manifest.yaml~/.bohr/tools/trisol/current/trisol~/.bohr/tools/trisol/manifest.yaml
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package runs postinstall automatically.
- The hook downloads companion binaries and writes them under the user's ~/.bohr/tools directory.
- The wenyon download is accepted when the server omits a SHA-256 value, so install-time remote content is not always integrity-checked.
- The trisol server can be replaced through an environment variable.
Evidence against
- Writes are limited to the package-owned ~/.bohr/tools hierarchy.
- The hook contains no credential harvesting or data-upload logic.
- Trisol downloads are checked against a SHA-256 sidecar before installation.
- The command launcher only invokes the matching optional platform package.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
9 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 unpkgpostinstall.jsView file
189try {
L190: const { execFileSync } = require("child_process");
L191: const out = execFileSync(destPath, ["version"], { encoding: "utf8", timeout: 5000 });
High
Findings
8 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processpostinstall.js
HighInstall Named Payload Filepostinstall.js
HighRuntime Package Installrun.js
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
HighKnown Malware Source Similaritypostinstall.js
HighKnown Malware Source Similarityrun.js
HighKnown Malware Source Fingerprint Signaturepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.6.89.
See all versions of @dptech-corp/bohr-cli for other recorded verdicts.
- Review the evidence and your use of @dptech-corp/bohr-cli@2.6.89 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.