Serious Security Breach + Evidence of Timeline Tampering – Forensic Update (Part 2) Riyad Bank Mastercard renewal chain: old card *1174 remained active → leaked/activated on Amazon.com US 14 May 2025 (01:56:59). New card *1233 sent with wrong mobile number → leaked on Amazon 22 May 2025 (22:58:45) while In_Transit/Returned. Latest Aramex statement (see attached "Aramex ENG.jpg"): - Shipments allegedly returned to Riyad Bank on **different dates** (first ~19 May 2025 or earlier, second later). The bombshell: When pressed on inconsistencies, Aramex **modified/edited both shipment return records** to show the **exact same return date, time, and second**: • Shipment 49715021705 (renewal *1233): Returned 20 Jul 2025 15:15:57 • Shipment 49715146165 (re-sent *1233): Returned 20 Jul 2025 15:15:57 Both shipments rescheduled to **identical timestamp** - despite: - Different tracking numbers - Different handover dates to Aramex (12 May vs 22 May 2025) - First shipment supposedly already returned to bank weeks earlier (around 19 May 2025) How is this possible? - Post-facto database edit / override to align records and hide chain-of-custody gaps? - Attempt to retroactively "fix" conflicting logs after customer pressure? This is no longer just a data leak - it's **potential evidence tampering** on top of upstream credential exposure. Recap Logic & Probability: IF (Card == In_Transit / Transition) ∧ (Enrolled_on_Amazon == TRUE) THEN Internal_Data_Stream (Bank → Amazon) → Internal_Leak = TRUE P(Internal_Leak) → 1.0 (transition exposure + logistics mishandling + now timeline manipulation) Compliance & Integrity Flags: • PCI DSS §7 – Access Control Failure • ISO 27001 A.13 – Data Transfer & Integrity • Potential violation of data record authenticity rules (tampering indicators) Pattern of Negligence → Exploitation: - Wrong mobile from shipper → no contact → failed delivery - Re-issue with same flaw after complaint - Automatic replacement (*1795) + forced fees despite "suspend only" request - Now: synchronized fake timelines to deflect scrutiny @RiyadBank @Aramex @AmazonHelp @Mastercard @FTC Why were both unrelated shipment returns edited to the **exact same second** (20 Jul 2025 15:15:57)? Was this a system correction, manual override, or attempt to conceal earlier return discrepancies? How can credentials leak on Amazon **before** logistics handover - twice? Full root-cause investigation + unaltered logs required - publicly. See you after Eid Al-Fitr. The waves are raging. 🔥 #DataBreach #TimelineTampering #PCIDSSViolation #CFPB #FTC #RiyadBank #Aramex #Amazon #تسريب_بيانات #ثمّن_بياناتك
