registry / @dptech-corp/bohr-cli / 2.6.86
@dptech-corp/bohr-cli@2.6.86
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an automatic remote-binary installer for a first-party Bohr tool directory, creating a supply-chain risk that warrants a warning. The inspected source does not establish malicious intent or a concrete exfiltration or destructive chain.
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 compromised or redirected vendor download path could stage executable code on the user's machine.
Mechanism
Remote binary download and executable installation into a user tool directory.
AI rationale
This is an automatic remote-binary installer for a first-party Bohr tool directory, creating a supply-chain risk that warrants a warning. The inspected source does not establish malicious intent or a concrete exfiltration or destructive chain.
Evidence
package.jsonpostinstall.js~/.bohr/tools/wenyon/current/wenyon-cli~/.bohr/tools/trisol/current/trisol
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The automatic postinstall hook fetches companion binaries from remote services.
- It writes executable downloads into the user's ~/.bohr tool directories.
- The Wenyon download URL is supplied by remote release metadata and redirects are followed.
Evidence against
- No credential harvesting, secret exfiltration, self-dependency, or project-file mutation was found.
- The launcher only resolves and executes 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.86.
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.86 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.