@dptech-corp/bohr-cli@2.6.42
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic install hook downloads and installs executable payloads, with conditional integrity checking for one download path. This is a real supply-chain risk, but the inspected source does not establish malicious execution or another concrete attack, so warn rather than block.
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 installation triggers the postinstall hook.
Impact
A compromised or untrusted release response could place an executable tool for later use; the inspected code does not show automatic execution of the newly downloaded binaries.
Mechanism
The hook fetches release metadata and binaries over HTTP(S), then writes them to tool directories and marks them executable; trisol uses a fetched SHA-256 value, while wenyon checks a hash only when metadata provides one.
AI rationale
The automatic install hook downloads and installs executable payloads, with conditional integrity checking for one download path. This is a real supply-chain risk, but the inspected source does not establish malicious execution or another concrete attack, so warn rather than block.
Evidence
package.jsonpostinstall.js~/.bohr/tools/trisol/current~/.bohr/tools/wenyon/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
- package.json runs postinstall.js automatically during installation.
- postinstall.js downloads executable tools and installs them under the user's home directory; trisol is verified against a fetched hash.
- wenyon metadata supplies the download URL, and its hash check is conditional.
- run.js resolves a platform-specific package binary and runs it with the caller's arguments.
Evidence against
- The inspected launcher delegates to the platform package binary and forwards its exit status.
- No credential collection, consumer-project mutation, or direct execution of newly downloaded binaries was identified in the inspected excerpts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
UrlStrings
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 unpkgpostinstall.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @dptech-corp/bohr-cli@2.6.100
matchedIdentity = npm:QGRwdGVjaC1jb3JwL2JvaHItY2xp:2.6.100
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
postinstall.jsFindings
1 Critical5 High4 Medium3 Low
CriticalPrevious Version Dangerous Deltapostinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processpostinstall.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
LowUrl Strings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.6.42.
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.42 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.