registry / twzrd-x402-gate / 0.9.16

twzrd-x402-gate@0.9.16

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.16. 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 version has a documented payment TOCTOU risk in its safe-fetch CLI: the challenge scored by the gate may differ from the one AgentCash signs. The behavior requires an explicit CLI invocation, but the mismatch can bypass the preflight's recipient or amount check, so warn users rather than block the package as malicious.

Static reason

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

Trigger

A user runs safe-fetch on a URL, the first 402 challenge is approved, and the user has not selected dry-run or preflight-only mode.

Impact

A changed challenge could charge a different recipient, network, asset, or amount than the one that passed preflight.

Mechanism

It preflights the first request's payment requirements, then invokes AgentCash, which makes a second request and may sign a different challenge without another gate check.

AI rationale

Evidence

dist/safe-fetch.jsbin/twzrd-safe-fetch.js

Network endpoints2

intel.twzrd.xyz/v1/intel/preflightUser-supplied target URL, requested through both the initial fetch and AgentCash

Decision evidence

public snapshot

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

Evidence for warning

The safe-fetch documentation says it preflights challenge A, then AgentCash makes a second request and may sign a different challenge B without rechecking it.
After the preflight allows payment, safe-fetch invokes AgentCash against the supplied URL, creating the second-request payment path.
The package has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly release verification.

Evidence against

The TOCTOU limitation is explicitly documented, and the CLI is described as an advisory precheck rather than a secure payment firewall.
The payment path is triggered by a user running the safe-fetch CLI; dry-run and preflight-only modes stop before payment.

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.16.

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

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

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

registry / twzrd-x402-gate / 0.9.16

twzrd-x402-gate@0.9.16

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 runs safe-fetch on a URL, the first 402 challenge is approved, and the user has not selected dry-run or preflight-only mode.

Impact

A changed challenge could charge a different recipient, network, asset, or amount than the one that passed preflight.

Mechanism

It preflights the first request's payment requirements, then invokes AgentCash, which makes a second request and may sign a different challenge without another gate check.

AI rationale

Evidence

dist/safe-fetch.jsbin/twzrd-safe-fetch.js

Network endpoints2

intel.twzrd.xyz/v1/intel/preflightUser-supplied target URL, requested through both the initial fetch and AgentCash

Decision evidence

public snapshot

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

Evidence for warning

The safe-fetch documentation says it preflights challenge A, then AgentCash makes a second request and may sign a different challenge B without rechecking it.
After the preflight allows payment, safe-fetch invokes AgentCash against the supplied URL, creating the second-request payment path.
The package has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly release verification.

Evidence against

The TOCTOU limitation is explicitly documented, and the CLI is described as an advisory precheck rather than a secure payment firewall.
The payment path is triggered by a user running the safe-fetch CLI; dry-run and preflight-only modes stop before payment.

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.16.

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

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

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