惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
Blog — PlanetScale
Blog — PlanetScale
GbyAI
GbyAI
C
Check Point Blog
腾讯CDC
Stack Overflow Blog
Stack Overflow Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
Recent Announcements
Recent Announcements
L
LangChain Blog
Microsoft Azure Blog
Microsoft Azure Blog
小众软件
小众软件
J
Java Code Geeks
博客园_首页
Jina AI
Jina AI
美团技术团队
H
Help Net Security
MyScale Blog
MyScale Blog
Engineering at Meta
Engineering at Meta
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
人人都是产品经理
人人都是产品经理
Y
Y Combinator Blog
S
SegmentFault 最新的问题

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Fraud Detection Was Built to Catch Humans. AI Agents Just...
Kavin Kim · 2026-06-17 · via DEV Community

Kavin Kim

Mastercard published it plainly: "As AI agents shop and pay on behalf of consumers, the payments ecosystem is tackling challenges around intent, fraud prevention and accountability."

The Merchant Risk Council went further: legitimate AI agents and fraudulent AI agents produce identical behavioral signals. The tools built to distinguish honest humans from dishonest humans cannot distinguish honest agents from dishonest agents.

RisingWave documented seven fraud patterns that human-written rules miss entirely in agentic payments. IBM responded by shipping MCP-based agent fraud detection. But the fundamental problem remains: fraud detection assumes the buyer is human. When the buyer is software, the detection model collapses.

Why Human Fraud Signals Do Not Work for Agents

Traditional fraud detection relies on behavioral signals that differentiate legitimate humans from fraudulent ones:

# Human fraud detection signals (all broken for agents):

human_fraud_signals = {
    "typing_speed": "Too fast = bot",
    # Agent: ALWAYS types at machine speed. Signal useless.

    "session_duration": "Too short = automated",
    # Agent: Completes checkout in 200ms. Always "too short."

    "mouse_movement": "Linear paths = bot",
    # Agent: No mouse. API calls only. Signal absent.

    "device_fingerprint": "New device = suspicious",
    # Agent: Runs on server. New "device" every session.

    "geographic_consistency": "VPN/proxy = risk",
    # Agent: Runs in cloud. IP is always a datacenter.

    "purchase_pattern": "Unusual category = risk",
    # Agent: Buys API credits, cloud compute, data feeds.
    # None match "normal human" purchase patterns.

    "time_of_day": "3 AM purchase = suspicious",
    # Agent: Runs 24/7. No "normal hours."
}

# Result: Every legitimate agent triggers EVERY fraud signal.
# False positive rate for agent transactions: approaching 100%.
# Merchants either block all agents or disable fraud detection.
# Neither option is acceptable at scale.

Hogan Lovells confirmed: "When an external AI agent is increasingly the shopper, both the merchant and payments provider sees less of the human and more of an automated request." The human behavioral layer that fraud detection depends on is simply absent.

The Agent Identity Problem

The core issue is not detecting fraud. It is proving legitimacy. A legitimate AI agent and a malicious AI agent look identical at the transaction layer:

# Legitimate agent transaction:
legitimate = {
    "buyer": "procurement_bot_v3",
    "owner": "acme_corp",
    "action": "purchase_api_credits",
    "amount": 450.00,
    "speed": "200ms",
    "ip": "35.201.x.x",  # GCP
    "session_age": "3 seconds",
    "prior_purchases": 47  # This week
}

# Malicious agent transaction (credential theft):
malicious = {
    "buyer": "procurement_bot_v3",  # Stolen identity
    "owner": "acme_corp",           # Spoofed
    "action": "purchase_api_credits",
    "amount": 450.00,
    "speed": "200ms",
    "ip": "35.201.x.x",            # Same cloud
    "session_age": "3 seconds",
    "prior_purchases": 47           # Matches pattern
}

# Traditional fraud detection: CANNOT distinguish these.
# Both are "software making fast purchases from a datacenter."
# The signal that would differentiate them: governance context.

# With rosud-pay agent identity + governance:
from rosud_pay import AgentIdentity, GovernanceProof

identity = AgentIdentity.verify(
    agent_id="procurement_bot_v3",
    proof=GovernanceProof(
        # Cryptographic proof of legitimate deployment
        deployment_signature="signed_by_acme_devops_key",

        # Real-time governance state
        current_budget_remaining=550.00,
        policy_version="v2.4.1",
        last_governance_check_ms=50,  # 50ms ago

        # Behavioral baseline (agent-native, not human-native)
        expected_purchase_categories=["api_credits", "cloud_compute"],
        expected_frequency="5-10_per_hour",
        expected_amount_range=[10, 500],

        # Delegation chain (who authorized this agent?)
        authorized_by="finance_team_policy_FP-2847",
        approval_timestamp="2026-06-15T09:00:00Z",
        expiry="2026-07-15T09:00:00Z"
    )
)

# Now fraud detection has AGENT-NATIVE signals:
# - Is this agent currently governed? (vs stolen credential with no governance)
# - Is it within its authorized budget? (vs unlimited stolen access)
# - Does it have a valid delegation chain? (vs spoofed identity)
# - Is its behavior within its AGENT baseline? (not human baseline)

Seven Patterns Human Rules Miss

RisingWave identified seven fraud patterns specific to agentic payments that rule-based systems cannot catch:

  1. Credential rotation attacks (agent switches wallets faster than rules update)
  2. Micro-transaction draining (thousands of sub-threshold purchases)
  3. Cross-agent collusion (multiple agents coordinating to stay under individual limits)
  4. Context manipulation (feeding false context to make agent authorize larger purchases)
  5. Governance bypass (agent operating after governance token expired)
  6. Shadow agent spawning (unauthorized copies of legitimate agent credentials)
  7. Replay attacks (re-submitting previously authorized transactions)

All seven require agent-native fraud detection. Not "is this human behavior suspicious?" but "is this agent operating within its governance boundaries?"

from rosud_pay import FraudDetection, AgentBaseline

# Agent-native fraud detection (not human-adapted):
fraud_engine = FraudDetection.configure(
    mode="agent_native",  # Not "human_adapted"
    checks={
        # Governance-based (unique to agents):
        "governance_token_valid": True,
        "within_authorized_budget": True,
        "delegation_chain_intact": True,
        "policy_version_current": True,

        # Agent behavioral baseline (not human behavioral):
        "frequency_within_baseline": True,
        "categories_within_scope": True,
        "amount_within_range": True,
        "cross_agent_coordination_check": True,

        # Cryptographic proofs:
        "deployment_signature_valid": True,
        "no_credential_duplication": True,
        "session_continuity_verified": True
    }
)

# Result: legitimate agents pass instantly (governance = proof of legitimacy)
# Malicious agents fail on governance checks (no valid delegation chain)
# False positive rate: <0.1% (vs ~100% with human-adapted rules)

The Bottom Line

Fraud detection was built for a world where the buyer is human. AI agents produce none of the behavioral signals that distinguish legitimate from fraudulent human activity. The result: either block all agent commerce or accept undetectable fraud.

rosud-pay provides agent-native fraud signals. Governance state as proof of legitimacy. Delegation chains as identity verification. Agent behavioral baselines instead of human behavioral baselines. The governance layer does not just control spending. It proves the agent is who it claims to be.

Legitimate agents have governance. Malicious agents do not. That is the only signal that works.


Prove your agents are legitimate: rosud.com/docs