@dptech-corp/bohr-cli@2.6.41
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe postinstall hook stages external executables and one path permits metadata without a hash, so a supply-chain risk remains. The inspected source ties this behavior to platform tools and does not show a concrete attack; downgrade to a warning.
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
The package’s postinstall lifecycle hook runs during installation.
Impact
A downloaded executable is staged for later use, creating a supply-chain exposure if the vendor metadata or download is compromised.
Mechanism
The installer fetches release metadata, downloads the supplied executable URL, and installs it; the Wenyon download hash is checked only if metadata includes one.
AI rationale
The postinstall hook stages external executables and one path permits metadata without a hash, so a supply-chain risk remains. The inspected source ties this behavior to platform tools and does not show a concrete attack; downgrade to a warning.
Evidence
package.jsonpostinstall.js
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 a postinstall script automatically during installation.
- Postinstall retrieves release metadata for an external platform tool.
- It downloads the metadata-provided executable URL and checks the hash only when metadata supplies one.
- The launcher resolves and invokes a platform-specific package binary.
Evidence against
- The downloads are tied to the Bohrium CLI’s platform tools and vendor endpoints.
- The inspected installer saves the downloaded executables but does not itself run them.
- The launcher delegates to the matching platform package binary; no credential collection or unrelated file mutation was identified.
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.41.
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.41 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.