registry / @dptech-corp/bohr-cli / 2.6.100
@dptech-corp/bohr-cli@2.6.100
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe active postinstall performs automatic companion CLI setup in the package’s own Bohr tool area, which warrants a warning under the lifecycle policy. Inspected source verifies a SHA-256 check before installation and does not show a concrete malicious attack chain.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package runs its postinstall hook.
Impact
Vendor-provided companion executables are added to the user's local Bohr tool installation.
Mechanism
The hook requests release metadata and downloads companion executables, verifies a SHA-256 value, then marks the file executable and stores it under the Bohr tools directory.
AI rationale
The active postinstall performs automatic companion CLI setup in the package’s own Bohr tool area, which warrants a warning under the lifecycle policy. Inspected source verifies a SHA-256 check before installation and does not show a concrete malicious attack chain.
Evidence
package.jsonpostinstall.js~/.bohr/tools/wenyon/current~/.bohr/tools/trisol/current
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs postinstall.js automatically during installation.
- The hook downloads companion CLI releases from the vendor’s HTTPS services and places them in the user’s Bohr tools directory.
- Downloaded files are checked against a SHA-256 value before being made executable and installed.
- The launcher forwards arguments to the platform-specific Bohr binary.
Evidence against
- Inspected source shows companion tools are installed in Bohr’s own tools directory, not a broad external agent configuration surface.
- The launcher resolves the platform binary and forwards arguments; no separate attack behavior was identified there.
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.100.
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.100 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.