registry / Remote code execution / @dptech-corp/bohr-cli
@dptech-corp/bohr-cli
CLI tool for Bohrium scientific computing platform
This report shows the evidence for @dptech-corp/bohr-cli@2.6.71. 2 of 94 known versions are blocked or flagged. The newest version, 2.8.1, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an automatic install-time remote code staging chain with later execution, not merely a user-invoked CLI action. The narrow .bohr destination and lack of secret harvesting reduce scope but do not remove the unconsented lifecycle execution risk.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation invokes postinstall; a later npm installation finds and runs the stored companion binary.
Impact
A service selected through an environment variable or redirect can supply code that is later executed during package installation.
Mechanism
Configurable remote binary staging followed by automatic execution.
Attack narrative
The postinstall hook selects a trisol server from BOHR_TRISOL_SERVER, follows redirects while downloading a binary, and stores it under ~/.bohr. On a later installation it invokes that stored binary with child_process. The hash is fetched from the same remote service and therefore does not provide an independently pinned trust boundary. Wenyon follows the same remote-download pattern and permits a metadata response without a hash.
AI rationale
This is an automatic install-time remote code staging chain with later execution, not merely a user-invoked CLI action. The narrow .bohr destination and lack of secret harvesting reduce scope but do not remove the unconsented lifecycle execution risk.
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 Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The install lifecycle automatically runs postinstall.js.
- Postinstall accepts a server address from an environment variable and downloads platform binaries into the user's home directory.
- The downloader follows redirects, writes executable files, and trusts hashes supplied by the same remote service.
- A later install lifecycle executes an already downloaded companion binary.
Evidence against
- The launcher only resolves and runs a matching optional platform package.
- No credential harvesting or unrelated project-file access was found.
- Download failures are handled without failing installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 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
5 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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.6.71.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dptech-corp/bohr-cli@2.6.71. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.