registry / @dptech-corp/bohr-cli / 2.6.84
@dptech-corp/bohr-cli@2.6.84
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has an automatic lifecycle downloader that installs remote executables into a vendor-managed Bohr tool location. Source inspection found no credential harvesting, exfiltration, self-dependency chain, or broad foreign agent configuration mutation, so blocking is not justified.
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 installation runs the postinstall lifecycle hook.
Impact
A remote service can select the downloaded companion executable and its redirect target before it is installed under ~/.bohr.
Mechanism
Remote companion-binary download and activation
AI rationale
The package has an automatic lifecycle downloader that installs remote executables into a vendor-managed Bohr tool location. Source inspection found no credential harvesting, exfiltration, self-dependency chain, or broad foreign agent configuration mutation, so blocking is not justified.
Evidence
package.jsonpostinstall.js~/.bohr/tools/trisol/current/trisol~/.bohr/tools/wenyon/current/wenyon-cli~/.bohr/tools/trisol/manifest.yaml~/.bohr/tools/wenyon/manifest.yaml
Network endpoints2
trisol.dp.techwenyon.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The npm postinstall hook runs automatically during installation.
- Postinstall fetches release metadata and binaries from remote vendor services.
- Downloaded executables are installed under the user's ~/.bohr tools directory.
- The downloader follows server-provided redirects, and the Wenyon binary URL comes from remote metadata.
Evidence against
- The code verifies SHA-256 values before activating downloaded binaries.
- No source in this package harvests credentials, reads unrelated user files, or exfiltrates data.
- No self-dependency, eval-style execution, or broad project configuration mutation was found.
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.84.
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.84 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.