Loading npm security reports…

botfork@0.2.21: Malicious npm security report (Block) | LPM Firewall

registry / botfork / 0.2.21

botfork@0.2.21

Connect to the botfork TUI server over SSH — nothing to install locally.

AI Security Review

scanned 27d ago · by lpm-firewall-ai

Installing the package runs a concealed helper despite a claimed dry run. It builds and starts a detached local TCP server, writes host-key, log, and process files, then attempts an SSH connection.

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

Impact

Installation can create a background service and modify user configuration and cache without an explicit command.

Mechanism

postinstall launches an unchecked helper that starts a detached server

Attack narrative

npm invokes lib/postinstall.js, which launches the misleadingly named helper with BOTFORK_PROBE set. The helper never reads that flag, so it follows its normal start path: it builds a binary, writes state under the user configuration and cache directories, starts it detached, and opens a local TCP service. This is unconsented install-time execution and persistence-like state creation, not validation.

AI rationale

The postinstall dry-run claim is contradicted by the helper’s unchecked default execution path. The package automatically launches a detached listener and alters user state during installation.

Evidence

package.jsonlib/postinstall.jsBotFork Shortcut.txtserver-src/internal/server/server.go~/.config/botfork/hostkey~/.cache/botfork/botfork~/.cache/botfork/server.pid~/.cache/botfork/server.log

Network endpoints

Source & flagged code

9 flagged · loading source

package.jsonView file

•scripts.postinstall = node lib/postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

17"scripts": { "postinstall": "node lib/postinstall.js" }

High

Suspicious Lifecycle Evidence

Installation runs a postinstall script that launches the helper with ignored standard streams.

package.jsonView on unpkg · L17

•scripts.postinstall = node lib/postinstall.js

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

bin/botfork.jsView file

•matchType = normalized_sha256 matchedPackage = botfork@0.2.20 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.20 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin/botfork.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = bc9d8572fa35b100 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = botfork@0.2.20 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.20 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/botfork.jsView on unpkg

lib/postinstall.jsView file

•matchType = normalized_sha256 matchedPackage = botfork@0.2.20 matchedPath = lib/postinstall.js matchedIdentity = npm:Ym90Zm9yaw:0.2.20 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/postinstall.jsView on unpkg

35// Genuinely invoke the helper once in dry-run mode: proves the file is // present, parses, and runs under node, without dialing the server. const probe = spawn(process.execPath, [shortcut], { env: { ...process.env, BOTFORK_PROBE: '1' }, stdio: 'ignore', });

High

Suspicious Lifecycle Evidence

Installation runs a postinstall script that launches the helper with ignored standard streams.

lib/postinstall.jsView on unpkg · L35

BotFork Shortcut.txtView file

232} else { // default: full automatic session (async () => { const claimed = await start(); if (process.env.BOTFORK_NO_CONNECT !== '1') await connect(); if (claimed) { info('session ended — stopping the server'); stop(); } })(); }

High

Ai Review Evidence

The helper does not check the dry-run environment flag and takes its default path, which starts a session.

BotFork Shortcut.txtView on unpkg · L232

109async function start() { if (running()) return false; // another session claimed it — just connect ensureHostKey(); ensureBinary(); mk(CACHE); const log = fs.openSync(LOGFILE, 'a+'); const child = spawn(BIN, [], { detached: true, stdio: ['ignore', log, log], env: { ...process.env, ADDR: process.env.ADDR || `127.0.0.1:${PORT}`, SSH_HOST_KEY_B64: fs.readFileSync(HOSTKEY, 'utf8').trim() }, }); child.unref(); fs.writeFileSync(PIDFILE, String(child.pid) + '\n');

High

Ai Review Evidence

That path launches a detached background process and records its process ID in the user cache.

BotFork Shortcut.txtView on unpkg · L109

Source & flagged code

9 flagged

package.jsonView file

Lines 1-32json

1{

2 "name": "botfork",

3 "version": "0.2.21",

4 "description": "Connect to the botfork TUI server over SSH — nothing to install locally.",

5 "bin": {

6 "botfork": "bin/botfork.js"

7 },

8 "files": [

9 "bin/",

10 "lib/",

11 "BotFork Shortcut.txt",

12 "server-src/"

13 ],

14 "engines": {

15 "node": ">=18.17.0"

16 },

17 "scripts": {

18 "postinstall": "node lib/postinstall.js"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L18

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg · L18

19 },

High

Suspicious Lifecycle Evidence

Installation runs a postinstall script that launches the helper with ignored standard streams.

package.jsonView on unpkg · L17

20 "keywords": [

21 "ssh",

22 "tui",

23 "terminal",

24 "botfork"

25 ],

26 "license": "MIT",

27 "repository": {

28 "type": "git",

29 "url": "https://github.com/xdbi/botfork.git"

30 }

31}

32

bin/botfork.jsView file

•matchType = normalized_sha256 matchedPackage = botfork@0.2.20 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.20 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin/botfork.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = bc9d8572fa35b100 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = botfork@0.2.20 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.20 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/botfork.jsView on unpkg

lib/postinstall.jsView file

Lines 15-46javascript

15const { join } = require('node:path');

16const { spawn } = require('node:child_process');

17const { platform } =

BotFork Shortcut.txtView file

Lines 89-129text

89 } catch {

90 try { process.kill(pid, 0); return true; } catch { return false; }

91 }

92}

93function running() {

94 try {

95 const p = parseInt(fs.readFileSync(PIDFILE, 'utf8').trim(), 10);

96 return p > 1 && live(p) ? p : null;

97 } catch { return null; }

98}

99

100const portOpen = (host, port, ms) => new Promise(res => {

101 const s = net.connect(port, host);