@dptech-corp/bohr-cli@2.6.90
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package transparently installs remotely selected executables during postinstall, including through redirects and an environment-overridable server. This warrants a warning, but the inspected source does not establish malicious intent or a concrete malicious payload.
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 postinstall.
Impact
A compromised or redirected release service could stage an executable for later use.
Mechanism
Remote binary download and home-directory installation.
AI rationale
The package transparently installs remotely selected executables during postinstall, including through redirects and an environment-overridable server. This warrants a warning, but the inspected source does not establish malicious intent or a concrete malicious payload.
Evidence
package.jsonpostinstall.js~/.bohr/tools/trisol/current/trisol~/.bohr/tools/trisol/manifest.yaml~/.bohr/tools/wenyon/current/wenyon-cli~/.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 automatic postinstall hook runs a network installer.
- The installer accepts an environment-selected trisol server and downloads its release manifest.
- It follows server-provided redirects and writes downloaded executables under the user's home directory.
- Checksums are obtained from the same remote release service rather than an embedded signing key.
Evidence against
- No credential harvesting or data exfiltration is present.
- The writes are limited to the package's .bohr tool directory.
- Downloaded files are hash-checked before installation.
- The launcher only executes a platform-specific optional dependency.
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.90.
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.90 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.