🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)
🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)

🔧 Programmierung 🕛 kürzlich 5 Min Lesezeit
0

Fraud Detection Was Built to Catch Humans. AI Agents Just Broke Every Rule It Relies On.

↗ Quelle (dev.to)
🗣️ Stimme:

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:




CODE
# 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:




CODE
# 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?"




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



Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Hackers Just Poisoned the Rust Supply Chain | Threat Wire
1 Quelle
Hackers Found a Way Into Humanoid Robots | Threat Wire
1 Quelle
Bits und so #1021 (Passwort für Laufwerk)
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Fraud Detection Was Built to Catch Humans. AI Agents Just Broke Every Rule It Relies On.

Thematisch verwandte Begriffe: Fraud, Detection, Built, Catch · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...