registry  /  hitmaker  /  2.0.1

hitmaker@2.0.1

Synthetic traffic generator for testing analytics, redirect, and click-tracking systems. Ships a prebuilt native binary with a Bubble Tea TUI and a headless CLI.

AI Security Review

scanned 2h ago · by lpm-firewall-ai

No confirmed malicious behavior in JavaScript source, but install-time code retrieves an unaudited native executable and the CLI executes it. Risk is unresolved because the binary is not included in the package source and has no integrity verification.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs postinstall; user invoking hitmaker runs bin/hitmaker.js.
Impact
Downloaded native code gains the privileges of the installing user when invoked; no source evidence of exfiltration or destructive behavior was found.
Mechanism
install-time native binary download and CLI spawn wrapper
Rationale
Static source inspection does not show concrete malware, exfiltration, persistence, destructive behavior, or AI-agent control-surface mutation. The unresolved risk is install-time acquisition and later execution of an unverifiable native binary, so warn rather than block.
Evidence
package.jsoninstall.jsbin/hitmaker.jsREADME.mdvendor/hitmakervendor/hitmaker.exe
Network endpoints2
github.com/zeb-link/hitmaker/releases/download/v2.0.1/hitmaker-{darwin|linux|windows}-{amd64|arm64}[.exe]github.com/zeb-link/hitmaker/releases

Decision evidence

public snapshot
AI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • package.json defines postinstall: node install.js.
  • install.js downloads a platform native binary from GitHub releases during install.
  • install.js writes vendor/hitmaker or vendor/hitmaker.exe and chmods it executable.
  • bin/hitmaker.js later spawnSyncs the downloaded native binary with user args.
  • No checksum/signature verification is present for the downloaded binary.
Evidence against
  • Only package files present are package.json, install.js, bin/hitmaker.js, README.md, and LICENSE.
  • Download host is package-aligned: github.com/zeb-link/hitmaker, matching repository/homepage.
  • No credential, env, home directory, npmrc, SSH, or token harvesting patterns found.
  • No broad filesystem mutation, persistence, AI-agent control-surface writes, or destructive code found.
  • README openly documents that the npm package downloads a prebuilt binary on install.
Behavioral surface
Source
ChildProcessFilesystemNetwork
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 2 file(s), 3.00 KB of source, external domains: github.com

Source & flagged code

2 flagged · loading source
package.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

Findings

1 High2 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
LowScripts Present
LowFilesystem
LowUrl Strings