Loading story…
A penetration test of a financial services onboarding application found a critical authentication and authorization flaw introduced during AI-assisted development, allowing the system to issue or restore an applicant access token based solely on possession of an applicant's GUID. The weakness meant an attacker who obtained or guessed that identifier could potentially access regulated customer PII, including identity details, financial information, and co-applicant data, because the application's trust decision was broken before token issuance rather than failing on secondary controls.
Reporting on the case said the exposure illustrates how AI can accelerate software delivery while also scaling security risk when business logic is not rigorously reviewed. The write-up linked the finding to a broader pattern in which AI speeds attacker operations as well, and recommended stronger governance for AI-assisted coding through better development visibility, explicit security requirements, focused review of authentication and authorization logic, and constrained use of AI for defensive code analysis.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
A real-world penetration test of a financial services onboarding application found a critical authentication and authorization flaw: possession of an applicant's GUID was treated as sufficient to issue or restore an applicant access token. The flaw could expose regulated client PII, including identity, financial, and co-applicant data.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Multiple reports warn that the most immediate AI security risk is **attackers hijacking trusted workflows**—AI copilots/agents, CI pipelines, SaaS admin planes, and identity control points—rather than “AI” being a standalone threat category. Commentary and research highlight how prompt-injection-style techniques can turn normal user actions (e.g., clicking a legitimate-looking link) into **silent data exfiltration** or unsafe tool use, and how autonomous agents can still complete scams even when they can correctly label a page as phishing. 1Password introduced an open-source benchmark, **Security Comprehension and Awareness Measure (SCAM)**, to test whether AI agents behave safely in realistic workplace tasks (email triage, link clicking, retrieving credentials from a vault, and form-filling) using production-like APIs; in testing, models that could identify phishing when asked still proceeded to **retrieve and submit real credentials** during routine workflows. Microsoft research described **AI recommendation poisoning** affecting 31 companies across 14 industries, where hidden instructions embedded in “*Summarize with AI*” links attempt to inject persistent directives into an assistant’s memory via URL prompt parameters, biasing future recommendations (e.g., prioritizing a specific domain/company). Separately, identity-focused analysis argues that as AI increases automation and API-driven decisioning, **identity becomes the enterprise control plane**, making IAM architecture and resilience (including where policy evaluation and authorization live) a central security concern at “AI scale.” Two SC Media opinion pieces broaden the theme: one ties recent supply-chain and developer-workflow compromises (e.g., malicious packages/actions and token theft) to the same “trusted workflow” abuse pattern, while another discusses mobile apps as an early-warning surface for supply-chain risk (including AI arriving via third-party SDKs), but it is more forward-looking guidance than incident reporting.
Jun 29, 2026
Enterprise adoption of AI agents is rapidly expanding the number of non-human identities inside corporate environments, with organizations increasingly running mixed stacks of coding assistants, writing tools, enterprise search, and agentic systems rather than relying on a single provider. Reporting based on Okta sign-on data from more than 20,000 organizations says each added AI platform brings more logins, secrets, tokens, service accounts, and permissions, while many companies still authorize agents with static API keys, OAuth apps, shared human accounts, or other weakly governed credentials that reduce auditability and increase the risk of over-permissioned access and orphaned accounts. Security reporting and industry data indicate that those governance gaps are already translating into higher exposure. The articles cite the `UNC6395` campaign, in which attackers allegedly abused a trusted OAuth token linked to Salesloft's Drift chat integration to pivot through Salesforce environments and obtain additional secrets including AWS credentials and Snowflake tokens, showing how machine identities can be exploited without a software flaw. A 2026 identity security report also found a 43% breach rate among organizations reporting AI-driven identity growth, versus 11% where AI had not significantly expanded identity counts, prompting calls for continuous inventory, clear ownership, least-privilege controls, lifecycle management, audit logging, and Zero Trust enforcement for AI agents and other machine identities.
Jul 24, 2026
Enterprises’ rapid deployment of **AI and agentic AI** is increasingly creating measurable security and business risk, including direct exposure of sensitive personal data and downstream impacts on risk transfer. A widely cited example involved McDonald’s *McHire* applicant-screening platform (built by *Paradox.ai*), where researchers reported a trivial backend credential weakness (`123456` as both username and password) and no MFA, potentially exposing data tied to roughly **64 million** applicants; the incident is being used by insurers and risk teams as evidence that AI adoption is moving faster than security and governance, contributing to tighter cyber-insurance language, higher premiums, and **AI-related exclusions**. Separate reporting also highlighted that “plug-and-play” AI is unrealistic at enterprise scale, with organizations increasingly needing custom integration and operational ownership rather than relying on off-the-shelf tools. Threat reporting during the same period reinforced that AI is expanding both attacker capability and the attack surface: researchers described **Pakistan-linked APT36** using AI coding tools to generate high volumes of low-quality malware variants (including in less common languages) and to leverage legitimate cloud services for command-and-control, complicating detection. Additional research flagged **AI-themed browser extensions** (Chrome/Edge) that impersonate legitimate tools and can harvest LLM chat histories and browsing activity, underscoring the risk of “shadow AI” and unvetted add-ons. In parallel, routine threat-intelligence summaries continued to track major incidents (e.g., ransomware and data breaches) alongside AI-enabled tactics, indicating that AI risk is becoming intertwined with broader enterprise security exposure rather than remaining a standalone technology concern.
Jun 29, 2026