Notifications
Clear all
Topic starter
31/07/2026 4:39 pm
TL;DR: Coordinated disruption of The Com, new isolation guidance for critical infrastructure OT, Telegram-related legal action, App Store crypto fraud allegations, and AI evaluation failures that reached live systems are the focus of a roundup, according to SentinelOne. The common thread is governance drift: trusted platforms, test environments, and identity controls all failed where abuse depended on overreach and weak containment.
NHIMG editorial — based on content published by SentinelOne: The Good, The Bad, and The Ugly roundup covering AI, fraud, and resilience incidents
By the numbers:
- 4000 URLs were flagged for removal in a, in a joint effort to disrupt the online ecosystem of The Com.
Questions worth separating out
Q: What breaks when AI agents or evaluation workloads are not tightly contained?
A: What breaks is the assumption that a sandbox, eval runner, or test environment can be treated as safe simply because it is internal.
Q: Why do trusted platforms still fail to stop fraud and abuse?
A: Trusted platforms fail when the trust signal is stronger than the verification behind it.
Q: How should organisations prepare for isolation of critical systems during a severe attack?
A: Organisations should predefine who can isolate systems, how the disconnect happens, and what operations continue after isolation.
Practitioner guidance
- Harden AI evaluation harnesses Remove live internet access, split test and production credentials, and require separate non-production identities for every third-party evaluation environment.
- Verify marketplace provenance before trust-sensitive installs Require independent checks for app origin, developer identity, and signing history before users enter seed phrases, API keys, or recovery materials.
- Test OT isolation as an executable runbook Document the physical and logical disconnect steps, assign decision authority, and rehearse manual fallback operations under realistic outage conditions.
What's in the full analysis
SentinelOne's full article covers the operational detail this post intentionally leaves for the source:
- The legal and incident context around the Telegram action and the related law-enforcement disruption effort
- The Apple App Store fraud allegations and the sequence that led victims to reveal seed phrases
- The Anthropic evaluation incident details, including the harness misconfiguration and package publishing path
- The critical infrastructure OT isolation guidance and the scenarios it is intended to support
👉 Read SentinelOne's roundup on AI evaluation failures, platform fraud, and OT resilience →
AI systems and fraud risks: what should practitioners re-evaluate now?
Explore further
31/07/2026 5:21 pm
Control failure is the real story here, not model capability. The AI incidents described in this roundup show that a misconfigured harness can be more dangerous than the model it contains. When live internet access, real credentials, or external package publishing are available, the environment becomes the attacker surface. Practitioners should treat evaluation infrastructure as a governed production-adjacent zone, not a disposable sandbox.
A few things that frame the scale:
- 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: Why do generative AI tools create non-human identity risk?
A: Generative AI tools create NHI risk because they often have access to corporate data, APIs, and workflows while operating outside traditional user-account models. The risk is not only prompt misuse. It is also the access identity behind the tool, the secrets it uses, and whether the organisation can see and constrain its reach.
👉 Read our full editorial: AI systems, fraud, and operational resilience: what this news means
