--- canonical: "https://firewall.lpm.dev/npm/@gethookmyapp/cli/v/0.14.29" markdown: "https://firewall.lpm.dev/npm/@gethookmyapp/cli/v/0.14.29.md" package: "@gethookmyapp/cli" report_status: "published" title: "@gethookmyapp/cli@0.14.29 npm security report" verdict: "suspicious" version: "0.14.29" --- # @gethookmyapp/cli@0.14.29 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Flagged — allowed with a warning** — Allowed by default policy, but 18 finding(s) warrant review before installing. - **Verdict:** Suspicious - **Product-default install policy:** Warn - **Firewall policy:** Telemetry warning (can be blocked) - **Public report status:** Published - **Threat category:** Telemetry - **Selected version:** 0.14.29 - **Selected version is latest:** Yes - **Analysis source:** AI Security Review (lpm-firewall-ai) This is the current Firewall decision for the selected package version, based on the available public evidence. Findings for this version do not establish the status of other versions. AI assessment: suspicious; recommendation: downgrade to warn. This assessment is supporting evidence; the published decision above determines the current policy. The CLI's default crash reporting attaches the logged-in account's email and user ID to Sentry events. This behavior is disclosed and can be disabled, but identifying details in runtime telemetry warrant a warning. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Suspicious - **Recorded analysis confidence:** 91.0% - **Started:** 2026-11-02T12:00:59.318Z - **Finished:** 2026-11-02T12:01:56.584Z - **Download time:** 768 ms - **Static scan time:** 5697 ms - **AI review time:** 50800 ms - **Total time:** 57266 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** Default runtime crash telemetry sends logged-in account identifiers to Sentry; no attack was identified beyond this privacy risk. - **Trigger:** A CLI error eligible for capture, while telemetry is enabled. - **Impact:** The telemetry provider receives identifying account details with crash reports. - **Evidence paths:** dist/cli.js - **Review source:** ai\_review - **Reviewed:** 2026-11-02T12:01:56.584Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** The CLI reads the saved access token or credential email, extracts the account subject and email, and attaches them to a Sentry crash report. - **Rationale:** The CLI's default crash reporting attaches the logged-in account's email and user ID to Sentry events. This behavior is disclosed and can be disabled, but identifying details in runtime telemetry warrant a warning. - **Files touched:** dist/cli.js - **Network endpoints:** https://4abeaf940e214f8c69d1af0f3ae800f7@o4511121201627136.ingest.de.sentry.io/4511251477561424 ### Review decision - **Verdict:** Suspicious - **Confidence:** 91.0% - **Recommended action:** downgrade\_to\_warn - **Intent class:** Dangerous Capability - **False-positive risk:** Medium - **Evidence for warning:** Crash reports sent to Sentry include the logged-in account's email and user ID., Telemetry is enabled unless disabled in config or with HOOKMYAPP\_TELEMETRY=off., Telemetry includes a Sentry endpoint and the package also discloses the account identifiers sent with crash reports. - **Evidence against:** The package discloses crash and usage telemetry, including the account identifiers attached to crash reports., The disclosure says command arguments, file contents, and environment variable values are not sent, except feedback submitted intentionally., Telemetry can be disabled through config or HOOKMYAPP\_TELEMETRY=off., The CLI's production API profile uses HookMyApp's own API host; review found no confirmed unrelated credential redirect. ## Affected versions and remediation This report applies to @gethookmyapp/cli@0.14.29. - Review the evidence and your use of @gethookmyapp/cli@0.14.29 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. ## Public findings ### 1. Low: Non Install Lifecycle Scripts - **Category:** Manifest - **Confidence:** 80.0% Package declares lifecycle scripts that are not normally run for registry tarball installs. ### 2. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 3. High: Child Process - **Category:** Source - **Confidence:** 85.0% - **Path:** dist/cli.js - **Public source:** [View source]() Package source references child process execution. Public source snippet (untrusted): ```javascript L1204: var EventEmitter = __require("node:events").EventEmitter; L1205: var childProcess4 = __require("node:child_process"); L1206: var path3 = __require("node:path"); ``` ### 4. Medium: Dynamic Require - **Category:** Source - **Confidence:** 75.0% - **Path:** dist/cli.js - **Public source:** [View source]() Package source references dynamic require/import behavior. Public source snippet (untrusted): ```javascript L2: import { createRequire } from "module"; L3: const require = createRequire(import.meta.url); L4: var __create = Object.create; ``` ### 5. Medium: Network - **Category:** Source - **Confidence:** 75.0% Package source references network APIs. ### 6. Medium: Environment Vars - **Category:** Source - **Confidence:** 75.0% Package source references environment variables. ### 7. Low: Filesystem - **Category:** Source - **Confidence:** 70.0% Package source references filesystem APIs. ### 8. Critical: Credential Exfiltration - **Category:** Source - **Confidence:** 90.0% - **Path:** dist/cli.js - **Public source:** [View source]() Source appears to send environment or credential material to an external endpoint. Public source snippet (untrusted): ```javascript L48: * Constructs the CommanderError class L49: * @param {number} exitCode suggested exit code which could be used with process.exit L50: * @param {string} code an id string representing the error ... L1204: var EventEmitter = __require("node:events").EventEmitter; L1205: var childProcess4 = __require("node:child_process"); L1206: var path3 = __require("node:path"); ... L1254: this._outputConfiguration = { L1255: writeOut: (str2) => process19.stdout.write(str2), L1256: writeErr: (str2) => process19.stderr.write(str2), ... L1296: * @returns {Command[]} L1297: * @private L1298: */ ``` ### 9. High: Credential Redirect Persistence - **Category:** Source - **Confidence:** 94.0% - **Path:** dist/cli.js - **Public source:** [View source]() Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection. Public source snippet (untrusted): ```javascript Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration. dist/cli.js: safeWriteFileSync: () => safeWriteFileSync import { writeFileSync, mkdirSync, existsSync, renameSync } from "node:fs"; function safeWriteFileSync(path3, data) { writeFileSync(path3, data); safeWriteFileSync(path3, JSON.stringify(secrets, null, 2)); `${API_KEY_ENV_VAR} is not a valid API key (expected it to start with "hmok_"). Fix or unset the variable, then retry.` safeWriteFileSync(getConfigFile(), JSON.stringify(cfg, null, 2) + "\n"); safeWriteFileSync(getConfigFile(), JSON.stringify(next, null, 2)); ``` ### 10. High: Command Output Exfiltration - **Category:** Source - **Confidence:** 82.0% - **Path:** dist/cli.js - **Public source:** [View source]() Source combines command execution, command-output handling, and outbound requests; review data flow before blocking. Public source snippet (untrusted): ```javascript L48: * Constructs the CommanderError class L49: * @param {number} exitCode suggested exit code which could be used with process.exit L50: * @param {string} code an id string representing the error ... L1204: var EventEmitter = __require("node:events").EventEmitter; L1205: var childProcess4 = __require("node:child_process"); L1206: var path3 = __require("node:path"); ... L1254: this._outputConfiguration = { L1255: writeOut: (str2) => process19.stdout.write(str2), L1256: writeErr: (str2) => process19.stderr.write(str2), ... L1296: * @returns {Command[]} L1297: * @private L1298: */ ``` ### 11. Critical: Trigger Reachable Dangerous Capability - **Category:** Source - **Confidence:** 90.0% - **Path:** dist/cli.js - **Public source:** [View source]() A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior. Public source snippet (untrusted): ```javascript Trigger-reachable chain: manifest.bin -> bin/hookmyapp.js -> dist/cli.js L48: * Constructs the CommanderError class L49: * @param {number} exitCode suggested exit code which could be used with process.exit L50: * @param {string} code an id string representing the error ... L1204: var EventEmitter = __require("node:events").EventEmitter; L1205: var childProcess4 = __require("node:child_process"); L1206: var path3 = __require("node:path"); ... L1254: this._outputConfiguration = { L1255: writeOut: (str2) => process19.stdout.write(str2), L1256: writeErr: (str2) => process19.stderr.write(str2), ... L1296: * @returns {Command[]} L1297: * @private L1298: */ ``` ### 12. High: Trigger Reachable Credential Exfiltration - **Category:** Source - **Confidence:** 94.0% - **Path:** dist/cli.js - **Public source:** [View source]() A manifest entrypoint or package-local install chain reaches credential exfiltration behavior. Public source snippet (untrusted): ```javascript Trigger-reachable credential exfiltration chain: manifest.bin -> bin/hookmyapp.js -> dist/cli.js L48: * Constructs the CommanderError class L49: * @param {number} exitCode suggested exit code which could be used with process.exit L50: * @param {string} code an id string representing the error ... L1204: var EventEmitter = __require("node:events").EventEmitter; L1205: var childProcess4 = __require("node:child_process"); L1206: var path3 = __require("node:path"); ... L1254: this._outputConfiguration = { L1255: writeOut: (str2) => process19.stdout.write(str2), L1256: writeErr: (str2) => process19.stderr.write(str2), ... L1296: * @returns {Command[]} L1297: * @private L1298: */ ``` ### 13. Low: High Entropy Strings - **Category:** Supply Chain - **Confidence:** 55.0% Package source contains high-entropy string patterns. ### 14. Low: Telemetry - **Category:** Supply Chain - **Confidence:** 70.0% Package source references telemetry or analytics APIs. ### 15. Low: Url Strings - **Category:** Supply Chain - **Confidence:** 65.0% Package source contains URL literals. ### 16. Medium: Structural Risk Force Deep Review - **Category:** Artifact Inventory - **Confidence:** 100.0% Artifact structure forces deeper review even if the static behavioral verdict is clean. ### 17. High: Semantic Analysis Limited - **Category:** Scanner Coverage - **Confidence:** 100.0% - **Path:** dist/cli.js - **Public source:** [View source]() A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review. Public source snippet (untrusted): ```javascript stage = ast_semantic_analysis; reason = ast_alias_growth_limit_exceeded; limitedFiles = 1 ``` ### 18. High: Known Malware Source Similarity - **Category:** Static - **Confidence:** 97.0% - **Path:** dist/cli.js - **Public source:** [View source]() Source file is highly similar to a previously finalized malicious package; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = normalized_sha256 matchedPackage = mlclaw@0.12.8 matchedPath = dist/mlclaw.mjs matchedIdentity = npm:bWxjbGF3:0.12.8 similarity = 1.000 summary = normalized source hash matched finalized malicious source ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** Yes - **Published lifecycle scripts:** prepublishOnly - **Dependencies:** 12 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 9 - **Published dependency-graph edges:** 12 ### Published dependency entries - @inquirer/prompts ^7.0.0 (Dependency) - @sentry/node ^10.69.0 (Dependency) - cli-table3 ^0.6.5 (Dependency) - commander ^14.0.0 (Dependency) - nanoid ^5.1.7 (Dependency) - open ^11.0.0 (Dependency) - ora ^9.3.0 (Dependency) - picocolors ^1.1.1 (Dependency) - posthog-node ^5.29.6 (Dependency) - qrcode-terminal 0.12.0 (Dependency) - tar ^7.5.22 (Dependency) - update-notifier ^7.3.1 (Dependency) ## Package metadata - **Package:** @gethookmyapp/cli - **Ecosystem:** npm - **Version:** 0.14.29 - **License:** MIT - **Version published:** 2026-10-22T07:52:08.414Z - **Package first seen:** 2026-07-11T11:36:31.947Z - **Package last seen:** 2026-11-02T12:02:53.361Z - **Known versions:** 16 - **Latest version:** 0.14.29 - **Appeal under review:** No - **Description:** HookMyApp CLI, No BS. Just go live. - **Maintainers:** hookmyapp - **Keywords:** whatsapp, whatsapp-business-api, webhook, cli, hookmyapp - **Runtime engines:** node: \>=20 - **Artifact files:** 5 - **Artifact unpacked size:** 2,486,800 bytes - **Artifact signatures:** 2 - **Attestations:** Yes - **Provenance:** https://slsa.dev/provenance/v1 ## References - [HTML security report]() - [Repository]() - [Homepage]() - [Issues]()