Staging Lambda called itself recursively via misconfigured trigger for ~6 hours; ~$1.8k bill spike; low-traffic persistence hid it.
Request sent to https://sipi.bot/v1/transactions/evaluate on 2026-08-30T15:36:17.558249+00:00:
{
"transaction_id": "replay-it-007-1788104177",
"amount": 1800.0,
"currency": "USD",
"merchant": "aws-lambda",
"description": "Replay of publicly reported incident amount (~$1,800, 2025-07-07) from https://news.ycombinator.com/item?id=44489247"
}
Exact response:
{
"decision": "BLOCKED",
"reason": "Block any single transaction over $500",
"rule_id": "rul_eff79f00f6",
"triggered": [
{
"rule_id": "rul_eff79f00f6",
"rule_type": "per_transaction",
"action": "BLOCKED",
"label": "Block any single transaction over $500"
}
],
"transaction_id": "txn_c63a46bd9fda",
"amount": 1800.0,
"merchant": "aws-lambda",
"category": ""
}
For this replayed transaction proposal, the live sipi.bot endpoint returned BLOCKED with the rule shown above.
This is a replay of a publicly reported amount, not a claim about avoided losses. The decision shown is a timestamped observation of the public demo decision API for this single replayed proposal, not a statement about the historical incident or any party's account.
Source checked live at 2026-08-30T15:36:17.558249+00:00.