registry / @dptech-corp/bohr-cli / 2.6.82

@dptech-corp/bohr-cli@2.6.82

CLI tool for Bohrium scientific computing platform

AI Security Review

scanned 2mo ago · by lpm-firewall-ai

This is a real lifecycle remote-code delivery risk, but the source limits persistence to package-owned .bohr tools and does not show exfiltration, destructive behavior, or broad AI-agent control-surface mutation. It warrants a warning rather than a publication block under the first-party extension lifecycle policy.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

npm installation triggers postinstall.

Impact

A compromised configured service or overridden trisol endpoint could install an attacker-controlled executable that later runs through the managed tool path.

Mechanism

Postinstall remote binary download, hash comparison, and installation into .bohr tools.

AI rationale

Evidence

package.jsonpostinstall.js~/.bohr/tools/wenyon/current/wenyon-cli~/.bohr/tools/wenyon/manifest.yaml~/.bohr/tools/trisol/current/trisol~/.bohr/tools/trisol/manifest.yaml

Network endpoints2

wenyon.dp.techtrisol.dp.tech

Decision evidence

public snapshot

AI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.

Evidence for warning

The automatic postinstall hook runs a downloader.
It fetches executable tools during installation and marks them executable.
The trisol server can be overridden through an environment variable, and redirects are followed.
Downloaded hashes come from the same remote service rather than a package-pinned signature.
The installer writes managed tool binaries under the user's .bohr directory.

Evidence against

No credential collection, environment harvesting, or data exfiltration is present.
Writes are limited to package-owned .bohr tool directories.
Download failures are handled as non-fatal.
The normal launcher only runs the matching optional platform binary when the user invokes bohr.
There is no runtime dependency on another release of this package.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

Source & flagged code

9 flagged

package.jsonView file

Lines 1-29json

2 "name": "@dptech-corp/bohr-cli",

3 "version": "2.6.82",

4 "description": "CLI tool for Bohrium scientific computing platform",

5 "bin": {

6 "bohr": "run.js"

7 },

8 "scripts": {

9 "postinstall": "node postinstall.js"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L9

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L9

10 },

11 "keywords": [

12 "bohrium",

13 "scientific-computing",

14 "cli",

15 "paper-search",

16 "molecular-dynamics"

17 ],

18 "author": "DP Technology",

19 "license": "MIT",

20 "os": [

21 "darwin",

22 "linux",

23 "win32"

24 ],

25 "cpu": [

26 "x64",

27 "arm64"

28 ],

29 "files": [

postinstall.jsView file

Lines 1-28javascript

1#!/usr/bin/env node

2/**

3 * postinstall: downloads wenyon-cli and the trisol external edition

4 * (variant=bohrium) for the current platform.

5 * Runs after `npm install -g @dptech-corp/bohr-cli`.

6 * Failure is non-fatal — bohr-cli works without them, and `bohr extension install <tool>`

7 * can retry later.

8 */

9const https =

run.jsView file

Lines 44-84javascript

44 );

45}

47const ext = platform === "win32" ? ".exe" : "";

48const pkgName

run.js#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

run.js#virtual:normalized:round1View on unpkg

Source & flagged code

9 flagged · loading source

package.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 unpkg

postinstall.jsView file

189try { L190: const { execFileSync } = require("child_process"); L191: const out = execFileSync(destPath, ["version"], { encoding: "utf8", timeout: 5000 });

High

Child Process

Package source references child process execution.

postinstall.jsView on unpkg · L189

Findings

8 High4 Medium4 Low

HighInstall Time Lifecycle Scriptspackage.json

HighChild Processpostinstall.js

HighInstall Named Payload Filepostinstall.js

HighRuntime Package Installrun.js

HighSemantic Analysis Limitedrun.js#virtual:normalized:round1

HighKnown Malware Source Similaritypostinstall.js

HighKnown Malware Source Similarityrun.js

HighKnown Malware Source Fingerprint Signaturepostinstall.js

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

Affected versions and remediation

This report applies to @dptech-corp/bohr-cli@2.6.82.

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.82 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: 2026-09-04 02:56:40.309Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.