registry / twzrd-x402-gate / 0.9.14

twzrd-x402-gate@0.9.14

Security fixes: payment-verdict integrity issues fixed through 0.11.4 (see the 0.11.2, 0.11.3 and 0.11.4 changelogs). Upgrade to twzrd-x402-gate@0.11.4.

Released identity 0.9.14. Buyer-side x402 trust gate: free preflight before signing USDC to a merchant. On Solana mainnet and Base mainnet (eip155:8453), a missing payTo is not approved, a buyer preflight outage does not sign unless TWZRD_FAIL_OPEN=true,

AI Security Review

scanned 5d ago · by lpm-firewall-ai

This is a disclosed but material payment-gating weakness: approval applies to a probe challenge, not necessarily the challenge AgentCash signs. The user-triggered and clearly documented behavior does not establish malicious intent, but warrants a warning as a critical vulnerability.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user invokes safe-fetch on a URL whose preflight is approved and does not use dry-run mode.

Impact

A changed challenge could direct payment to a different recipient, network, or amount than the preflight approved.

Mechanism

The CLI probes the target and scores its 402 challenge, then starts AgentCash, which independently requests the target and handles payment without binding its challenge to the one scored.

AI rationale

Evidence

dist/safe-fetch.jsREADME.md

Network endpoints2

intel.twzrd.xyzCaller-supplied target URL

Decision evidence

public snapshot

AI called this Suspicious at 90.0% confidence as Critical Vulnerability with medium false-positive risk.

Evidence for warning

The safe-fetch flow preflights challenge A, then invokes AgentCash, which makes a second request that may present a different challenge B.
The implementation passes the caller's URL to AgentCash after approval; the README confirms the second request may differ in recipient, network, or amount.

Evidence against

The README prominently labels this CLI an advisory pre-check, warns it is not a challenge-bound firewall, and describes the TOCTOU risk.
The package has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly.
The risky payment path runs only when a user invokes safe-fetch; the package's documented secure integrations use a pre-payment hook.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

Source & flagged code

5 flagged

bin/twzrd-safe-fetch.jsView file

5*/ L6: import { spawnSync } from "node:child_process"; L7: import { existsSync } from "node:fs";

High

Child Process

Package source references child process execution.

bin/twzrd-safe-fetch.jsView on unpkg · L5

bin/twzrd-gate-eval-refuse.jsView file

28const pkgRoot = join(__dirname, ".."); L29: const require = createRequire(import.meta.url); L30:

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/twzrd-gate-eval-refuse.jsView on unpkg · L28

bin/twzrd-gate-doctor.jsView file

33// tsx resolves `src` by absolute path, so the user's cwd is safe to keep. L34: const r = spawnSync("npx", ["--yes", "tsx", src, ...process.argv.slice(2)], { L35: stdio: "inherit",

Findings

1 Critical3 High4 Medium5 Low

CriticalPrevious Version Dangerous Deltadist/safe-fetch.js

HighChild Processbin/twzrd-safe-fetch.js

HighRuntime Package Installbin/twzrd-gate-doctor.js

HighSemantic Analysis Limiteddist/evidence-verify.js#virtual:normalized:round1

MediumDynamic Requirebin/twzrd-gate-eval-refuse.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to twzrd-x402-gate@0.9.14.

See all versions of twzrd-x402-gate for other recorded verdicts.

Review the evidence and your use of twzrd-x402-gate@0.9.14 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-31 01:23:33.501Z (UTC).

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

registry / twzrd-x402-gate / 0.9.14

twzrd-x402-gate@0.9.14

Security fixes: payment-verdict integrity issues fixed through 0.11.4 (see the 0.11.2, 0.11.3 and 0.11.4 changelogs). Upgrade to twzrd-x402-gate@0.11.4.

AI Security Review

scanned 5d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user invokes safe-fetch on a URL whose preflight is approved and does not use dry-run mode.

Impact

A changed challenge could direct payment to a different recipient, network, or amount than the preflight approved.

Mechanism

The CLI probes the target and scores its 402 challenge, then starts AgentCash, which independently requests the target and handles payment without binding its challenge to the one scored.

AI rationale

Evidence

dist/safe-fetch.jsREADME.md

Network endpoints2

intel.twzrd.xyzCaller-supplied target URL

Decision evidence

public snapshot

AI called this Suspicious at 90.0% confidence as Critical Vulnerability with medium false-positive risk.

Evidence for warning

The safe-fetch flow preflights challenge A, then invokes AgentCash, which makes a second request that may present a different challenge B.
The implementation passes the caller's URL to AgentCash after approval; the README confirms the second request may differ in recipient, network, or amount.

Evidence against

The README prominently labels this CLI an advisory pre-check, warns it is not a challenge-bound firewall, and describes the TOCTOU risk.
The package has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly.
The risky payment path runs only when a user invokes safe-fetch; the package's documented secure integrations use a pre-payment hook.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

Source & flagged code

5 flagged

bin/twzrd-safe-fetch.jsView file

5*/ L6: import { spawnSync } from "node:child_process"; L7: import { existsSync } from "node:fs";

High

Child Process

Package source references child process execution.

bin/twzrd-safe-fetch.jsView on unpkg · L5

bin/twzrd-gate-eval-refuse.jsView file

28const pkgRoot = join(__dirname, ".."); L29: const require = createRequire(import.meta.url); L30:

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/twzrd-gate-eval-refuse.jsView on unpkg · L28

bin/twzrd-gate-doctor.jsView file

33// tsx resolves `src` by absolute path, so the user's cwd is safe to keep. L34: const r = spawnSync("npx", ["--yes", "tsx", src, ...process.argv.slice(2)], { L35: stdio: "inherit",

Findings

1 Critical3 High4 Medium5 Low

CriticalPrevious Version Dangerous Deltadist/safe-fetch.js

HighChild Processbin/twzrd-safe-fetch.js

HighRuntime Package Installbin/twzrd-gate-doctor.js

HighSemantic Analysis Limiteddist/evidence-verify.js#virtual:normalized:round1

MediumDynamic Requirebin/twzrd-gate-eval-refuse.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to twzrd-x402-gate@0.9.14.

See all versions of twzrd-x402-gate for other recorded verdicts.

Review the evidence and your use of twzrd-x402-gate@0.9.14 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-31 01:23:33.501Z (UTC).

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