@dptech-corp/bohr-cli@2.6.96
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an automatic lifecycle-installed remote executable payload, which creates a meaningful supply-chain risk. The inspected code lacks credential theft, immediate payload execution, broad foreign control-surface changes, or the self-dependency chain required for a malicious block verdict.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
npm postinstall
Impact
A server-selected executable is persisted for later use under the user's home directory.
Mechanism
Automatic remote binary download and executable installation
AI rationale
This is an automatic lifecycle-installed remote executable payload, which creates a meaningful supply-chain risk. The inspected code lacks credential theft, immediate payload execution, broad foreign control-surface changes, or the self-dependency chain required for a malicious block verdict.
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 Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Installation automatically runs a postinstall script.
- The postinstall script fetches companion-tool metadata and binaries from remote servers.
- It writes downloaded files under the home directory, marks them executable, and installs them without an explicit command.
- The trisol server can be overridden through an environment variable.
Evidence against
- The downloaded file is checked against a SHA-256 value before it is made executable.
- The inspected JavaScript does not harvest credentials, exfiltrate files, or execute the downloaded companion tools during installation.
- No self-dependency, obfuscation, or foreign AI-agent configuration mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 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
1 Critical5 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltapostinstall.js
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.96.
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.96 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.