SI AgentsV12 / x402 Foundation

x402 research exposes automated payment risks: agents need clear spending limits

V12 research says older x402 automated payment flows could accept excessive amounts requested by external services, and identifies payment and authentication-check issues. The official code has added spending controls, but users still need their own payment and permission policies.

Anti-Ransomware · Compiled with SI agent assistanceOriginal source publication date: 2026-10-22:Checked 2026.10.26
Original synthetic illustration of a conceptual installation showing automated payment tokens and a separate approval boundary
Illustration · Source ↗ · About this image ↗

Source Facts

x402 enables software or agents to pay automatically when calling APIs. V12's research of 22 October explains that older default flows without separate limits could pass the amount requested by the other party directly to a wallet for signing.

This resembles giving an assistant a task with payment authority without specifying how much it may spend each time. The research also discusses payment verification and cross-site login signing. These are findings from code inspection and local tests, not statistics on actual stolen funds.

V12 says three key issues were fixed in August. Official x402 changes also added a default US$1 limit per transaction and restrictions on approved assets. These settings can be changed and do not replace an organisation's own total budget and approval process.

Next Steps for Businesses / Editorial Observations

Before automatic payments, limit amounts, recipients and available assets

Next steps you can take

  • Check the x402 SDK actually in use, its version and official update history, then test normal payment flows after upgrading.
  • Set per-payment and total budgets, permitted recipients and assets. Retain human approval for significant payments.

Original sources

Reporting leads · The Hacker News

The original material listed above has been traced. Older media headlines may have been corrected; this article uses the verified facts and limitations.

25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings

Sources checked: 2026-10-26 · Prepared with SI agent assistance; articles have not been individually reviewed by a person.

This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.

Back to news ←

KEEP READING

Recommended reading

Related reports and practical guides selected for this article's topic.

Original synthetic illustration of a software package conveyor and a master key stored separatelyIllustrationSupply chain security · 2026.10.24

LiteLLM explains package compromise: exposed keys must be revoked to complete the response

LiteLLMOriginal synthetic illustration of incident response colleagues checking an event timeline and system accessIllustrationResearch reports · 2026.10.23

SOCRadar examines SI agent-assisted extortion: human approval remains part of the intrusion process

SOCRadar Threat Research UnitIllustration of separated network cables and ports on a workbench, representing isolation checksIllustrationSI Agents · 2026.10.23

OpenAI details training environment isolation improvements, using offline operation and continuous red teaming to constrain agents

OpenAI