@dptech-corp/bohr-cli@2.6.91
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not proven malware, but the automatic remote executable staging and pre-verification execution create a real lifecycle risk. The behavior is confined to the package's own tool area and no exfiltration was found.
Decision evidence
public snapshot- The package runs postinstall.js automatically after installation.
- The install hook downloads companion executables into the user's .bohr tool directory and marks them executable.
- The trisol server can be overridden by an environment variable, and download redirects are followed without a host allowlist.
- An existing companion executable is invoked for its version before its hash is checked.
- No credential harvesting or secret exfiltration appears in the inspected JavaScript.
- The launcher runs only after an explicit bohr command and delegates to the matching optional platform package.
- The observed writes are confined to the vendor's .bohr tool area rather than general project or agent configuration files.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
postinstall.jsFindings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.6.91.
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.91 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.