The install hook automatically executes an uninspectable vendor binary, so the package has a concrete install-time code execution path that cannot be verified from this snapshot. The README says a prebuilt CLI binary is pulled, and the visible hook only probes it with --version, but the executable itself remains uninspected.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install postinstall
Mechanism
The hook resolves an optional platform package or installs it through npm, copies its executable to bin/.megabrain, and invokes it with --version.
Attack narrative
During postinstall, the package selects or retrieves a platform binary, copies it into its bin directory, and executes it with --version. The README discloses that installation pulls a prebuilt binary for the CLI, but the binary itself was unavailable for inspection. The automatic execution of that uninspectable executable is the concern; the inspected JavaScript does not show unrelated collection or a separate endpoint.
Evidence
package.jsonpostinstall.mjsREADME.mdbin/.megabrainbin/tree-sitterbin/consolebin/bwrapbin/licensesbin/kilo-sandbox-mutation-worker.js