Skip to content
Tech News
← Back to articles

Identity-Based AI Attack Threatens Security of Enterprise Data

read original get Yubico YubiKey 5 NFC Security Key → more articles
Why This Matters

Noma Labs says enterprise AI pipelines contain an authorization design flaw: the identity of whoever triggers a workflow is decoupled from the powerful service credentials that execute it. That means an outsider emailing a public support inbox or filing a GitHub issue can get an AI workflow to fetch data they were never entitled to see, such as an executive's email. As companies wire LLMs into inboxes, forms, and internal systems, this turns ordinary entry points into data-exfiltration channels without any traditional 'hack.'

Key Takeaways
Worth a Look

Yubico YubiKey 5 NFC Security Key — When attacks hinge on identity and authorization gaps, hardware-backed authentication is a solid line of defense for the human side of the equation. The YubiKey 5 NFC plugs into USB-A or taps against a phone over NFC to confirm logins with a physical touch, supporting FIDO2/WebAuthn, OTP and smart card protocols across major work accounts. It's a durable, battery-free key that lives on your keyring and makes account takeover far harder.

See Yubico YubiKey 5 NFC Security Key on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

Security researchers have identified a new artificial intelligence (AI) attack flow that stems from what they say is an authorization design flaw in modern enterprise AI pipelines.

Called "workflow identity hijacking" by the researchers at Noma Labs who discovered it, the attack vector allows threat actors to bypass standard security controls by sending what seems to be a normal, benign request through an unauthenticated entry point, such as a support inbox, GitHub issue, Web form, or shared document, according to a report published today. The issue stems from how these AI pipelines decouple the identity and permission of the user who triggers the workflow and the permissions used to execute it.

"The enterprise AI pipeline reads the input, interprets the request, and executes the action exactly as designed," Sasi Levi, security research lead at Noma, wrote in the report. "The core failure is that the requester had no authority to make that request."

Related:Cybercriminals Hack Brazilian Government Servers to Host Phishing Sites

The researchers described an attack scenario in which a threat actor sends a message to an organization's public support email asking about their own account but also adding a question about what the finance director said in her last email.

"Minutes later, the contents of the Finance Director's most recent email arrive in the attacker's inbox," Levi wrote. "The company's AI workflow read the message, understood the request, searched for the requested information, and replied."

Understanding an AI Workflow Attack

The heart of why the authorization flaw exists lies in the distinction between AI workflows and agentic workflows, which, while often used interchangably, have fundamentally different execution models, according to Noma Labs.

An AI workflow is a fixed, predefined process where an LLM performs a specific task within a sequence of steps. The surrounding system determines what happens before and after the model, so the workflow itself remains largely predictable.

An agentic workflow is more autonomous: the AI agent decides dynamically what steps to take, which tools or systems to access, and how to achieve a particular goal based on the situation. In short, AI workflows follow a set path, while agentic workflows decide the path.

... continue reading