registry / @dptech-corp/bohr-cli / 2.6.98
@dptech-corp/bohr-cli@2.6.98
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis package has a real automatic remote-binary provisioning surface, but the source shows integrity checks and package-aligned companion-tool locations. It does not establish concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm install, including global installation, runs postinstall.
Impact
A vendor-controlled release response can cause a new companion binary to be stored as executable content for later use.
Mechanism
Automatic network download and verified staging of companion executables.
AI rationale
This package has a real automatic remote-binary provisioning surface, but the source shows integrity checks and package-aligned companion-tool locations. It does not establish concrete malicious behavior.
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 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The install lifecycle runs a script automatically.
- The script downloads companion executables during installation and writes them under the user's .bohr directory.
- The download URL for one companion is supplied by a network response, so installation stages remotely supplied executable content.
Evidence against
- The downloaded files are checked against required SHA-256 values before being made executable.
- The launcher only resolves a matching optional platform package and executes its local binary when the user invokes the CLI.
- No credential harvesting, secret exfiltration, shell execution, self-dependency, or agent-control configuration writes were found.
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 unpkgrun.jsView file
1#!/usr/bin/env node
L2: const { execFileSync } = require("child_process");
L3: const path = require("path");
High
64
Findings
5 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processrun.js
HighRuntime Package Installrun.js
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
HighKnown Malware Source Similarityrun.js
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.98.
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.98 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.