registry / botfork / 0.2.13

botfork@0.2.13

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

AI Security Review

scanned 27d ago · by lpm-firewall-ai

Installation automatically runs a disguised Node.js helper. The helper can build and launch a detached local server, write configuration and cache files, and invoke SSH despite the installer describing this as a dry run.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall

Impact

Can execute build tools, create a background process, write botfork files under user configuration and cache directories, and initiate an SSH connection during installation.

Mechanism

Install hook launches concealed server-management and SSH code.

Attack narrative

The package’s postinstall hook executes a helper intentionally disguised as a text file. Although the hook calls this a dry run and sets BOTFORK_PROBE, the helper never tests that variable. Its default path starts a detached server, may build a binary from a selected source directory, writes configuration and cache state, and invokes SSH. This is unconsented install-time execution with deceptive packaging.

AI rationale

The source directly contradicts the postinstall dry-run claim: the invoked helper takes its full server-start and SSH path. The deliberate concealment and automatic lifecycle execution establish malicious install-hook abuse.

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

Network endpoints1

botfork@0.2.13

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code