@dptech-corp/bohr-cli@2.6.83
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a concrete automatic remote-binary installation path outside the npm directory. Its scope is vendor tool storage and lacks confirmed theft, execution, obfuscation, or self-dependent lifecycle chaining, so it warrants a warning rather than a 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 installation runs the postinstall hook.
Impact
A compromised or redirected release service can place an executable in the user's Bohr tool directory.
Mechanism
Redirect-following remote binary download and installation.
AI rationale
The package has a concrete automatic remote-binary installation path outside the npm directory. Its scope is vendor tool storage and lacks confirmed theft, execution, obfuscation, or self-dependent lifecycle chaining, so it warrants a warning rather than a 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 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- An automatic postinstall hook runs postinstall.js.
- The hook fetches release metadata and binaries from vendor servers, follows redirects, and saves executable files under the user's home directory.
- Downloaded companion binaries become executable and are retained as managed tools outside the npm package.
Evidence against
- The launcher only runs the matching optional platform package; it does not install packages at runtime.
- No credential harvesting, environment exfiltration, shell execution, eval, or self-dependency was found.
- Trisol downloads are checked against a separately fetched SHA-256 value before installation.
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.83.
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.83 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.