@dptech-corp/bohr-cli@2.6.87
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real install-time remote-payload supply-chain risk, but the inspected code confines its writes to package-owned tool storage and does not establish a concrete malicious objective. The package should be warned rather than blocked.
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 malicious service response can place a replacement executable for later use.
Mechanism
Remote executable download and installation.
AI rationale
This is a real install-time remote-payload supply-chain risk, but the inspected code confines its writes to package-owned tool storage and does not establish a concrete malicious objective. The package should be warned rather than blocked.
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
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Installation automatically runs a downloader.
- The downloader follows redirects and saves remotely supplied executables.
- The reported checksum is fetched from the same unpinned service that selects the binary.
Evidence against
- Writes are limited to the vendor's ~/.bohr tool directory.
- The source contains no credential collection, project-file harvesting, or exfiltration.
- The normal CLI launcher only executes its 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.87.
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.87 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.