@metaphi-ai/hum@0.1.16

Hum (हम): a self-improving coding agent for your terminal.

AI Security Review

scanned 14d ago · by lpm-firewall-ai

Source inspection found an install hook that provisions the matching Python engine and a CLI that communicates with the Hum distribution host. The flagged credential collection claim was not supported by the inspected source; no concrete attack behavior was established.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

npm install runs the postinstall hook; running the hum command starts the bundled CLI.

Impact

These behaviors support the package’s stated terminal agent setup; inspected source does not show credential harvesting or unrelated data exfiltration.

Mechanism

The hook provisions uv and a version-matched hum-cli Python environment under the Hum home directory. The CLI uses the Hum distribution host for release checks and engine downloads.

AI rationale

Evidence

~/.hum/engine

Network endpoints3

astral.sh/uv/install.ps1astral.sh/uv/install.shstorage.googleapis.com/hum-dist

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The manifest’s postinstall runs a package setup script, and its launcher imports the bundled CLI.
The setup script installs the package’s Python engine into the Hum home directory; it does not install another release of this npm package.
The CLI uses a configurable Hum distribution host for release checks and engine downloads.

Evidence against

The reviewed CLI source does not establish browser credential collection or exfiltration; the inspected network behavior is for Hum release and engine operations.
The setup script’s shell command installs uv from its published installer endpoint, consistent with setting up the declared Python engine.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsTelemetryUrlStrings

Manifest

Source & flagged code

10 flagged

package.jsonView file

Lines 1-13json

2 "name": "@metaphi-ai/hum",

3 "version": "0.1.16",

4 "description": "Hum (हम): a self-improving coding agent for your terminal.",

5 "license": "UNLICENSED",

6 "type": "module",

7 "bin": { "hum": "bin/hum.js" },

8 "files": ["bin", "dist", "scripts"],

9 "scripts": { "postinstall": "node scripts/postinstall.js" },

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L9

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg · L9

10 "engines": { "node": ">=18" },

11 "repository": { "type": "git", "url": "git+https://github.com/metaphi-labs/hum-cli.git" }

12}

dist/cli.mjsView file

317"use strict"; L318: if (process.env.NODE_ENV !== "production") { L319: (function() { ... L545: isMounted: ["isMounted", "Instead, make sure to clean up subscriptions and pending requests in componentWillUnmount to prevent memory leaks."], L546: replaceState: ["replaceState", "Refactor your code to use setState instead (see https://github.com/facebook/react/issues/3236)."] L547: }; ... L2209: ]; L2210: if (process.platform !== "win32") { L2211: module.exports.push( ... L2357: } L2358: process13.exitCode = code || /* istanbul ignore next */ L2359: 0;

Critical

Browser Credential Phishing

Source appears to collect browser login credentials for exfiltration.

dist/cli.mjsView on unpkg · L317

31298/** @param {string} s */ L31299: exec(s) { L31300: this.matcherRe.lastIndex = this.lastIndex;

High

Child Process

Package source references child process execution.

dist/cli.mjsView on unpkg · L31298

56858L56859: // node_modules/highlight.js/lib/languages/powershell.js L56860: var require_powershell = __commonJS({

High

Shell

Package source references shell execution.

dist/cli.mjsView on unpkg · L56858

83597import path from "node:path"; L83598: import { spawn, spawnSync } from "node:child_process"; L83599: var dist = (env3 = process.env) => (env3.HUM_DIST || "https://storage.googleapis.com/hum-dist").replace(/\/+$/, ""); L83600: var humHome = (env3 = process.env) => env3.HUM_HOME || path.join(os3.homedir(), ".hum");

bin/hum.jsView file

8// a URL, not a path: on Windows `C:\…` is not something the ESM loader will import L9: await import(pathToFileURL(path.join(here, '..', 'dist', 'cli.mjs')).href);

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/hum.jsView on unpkg · L8

Source & flagged code

10 flagged · loading source

package.jsonView file

•scripts.postinstall = node scripts/postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node scripts/postinstall.js

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

dist/cli.mjsView file

Findings

1 Critical7 High5 Medium6 Low

CriticalBrowser Credential Phishingdist/cli.mjs

HighInstall Time Lifecycle Scriptspackage.json

HighChild Processdist/cli.mjs

HighShelldist/cli.mjs

HighSame File Env Network Executiondist/cli.mjs

HighSandbox Evasion Gated Capabilitydist/cli.mjs

HighRemote Agent Bridgedist/cli.mjs

HighKnown Malware Source Similaritydist/cli.mjs

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumDynamic Requirebin/hum.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

Affected versions and remediation

This report applies to @metaphi-ai/hum@0.1.16.

See all versions of @metaphi-ai/hum for other recorded verdicts.

Review the evidence and your use of @metaphi-ai/hum@0.1.16 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-09 06:55:09.203Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.