Incidents tagged pro

Autonomous AI trading agents in 2026 were compromised by protocol-level vulnerabilities such as memory poisoning and indirect prompt injection, targeting their long-term memory and execution protocols like the Model Context Protocol (MCP). These flaws facilitated over $45 million in crypto security breaches, including a $40 million drain from Step Finance amplified by excessive agent permissions.

TeamPCP orchestrated a sophisticated supply chain attack, compromising the Trivy security scanner's CI/CD pipeline to publish malicious versions of the LiteLLM AI proxy package to PyPI. These trojanized versions deployed a multi-stage payload for credential harvesting, Kubernetes lateral movement, and persistent remote code execution.

Architectural vulnerabilities within Large Language Model (LLM) environments integrated with the Model Context Protocol (MCP) enable attackers to embed malicious instructions within data content or tool metadata. This flaw allows for indirect prompt injection and tool poisoning, compelling LLMs to autonomously perform unauthorized actions such as data exfiltration or triggering enterprise workflows.

A viral AI caricature trend exposes enterprises to shadow AI risks and sensitive data leakage, as employees input work-related information into public LLMs and share results. This behavior enables adversaries to conduct targeted social engineering for LLM account compromise, granting access to confidential prompt histories.

Flickr experienced a data breach due to a security vulnerability found within a system managed by a third-party email service provider. This flaw potentially exposed user names, email addresses, IP addresses, and activity logs, though sensitive user passwords and financial information remained secure.

The article highlights a critical vulnerability in AI agents where simple prompt engineering can lead to the compromise of entire systems. This demonstrates the significant risk posed by prompt injection attacks, allowing adversaries to bypass intended security mechanisms within AI-driven applications.

Traditional security frameworks fail to address AI-specific attack vectors such as prompt injection, model poisoning, and AI supply chain compromises, creating significant security gaps. This inadequacy has enabled various exploits, including the Ultralytics AI library compromise for cryptomining and malicious Nx packages exfiltrating 23.77 million secrets in 2024.

Security researcher Ari Marzouk disclosed "IDEsaster," a collection of over 30 vulnerabilities, with 24 assigned CVEs, affecting various AI-powered Integrated Development Environments (IDEs) like GitHub Copilot and Cursor. These flaws enable attackers to chain prompt injection techniques with legitimate IDE features and auto-approved AI agent tool calls to achieve sensitive data exfiltration and remote code execution (RCE).

The article highlights critical security risks in Large Language Model (LLM) deployments, emphasizing prompt injection as a key attack vector where malicious inputs override an LLM's intended behavior. This can lead to sensitive data leakage, unauthorized actions, or the generation of harmful content, necessitating robust input validation and secure model deployment practices.

Threat actor UNC6395 exploited compromised OAuth and refresh tokens associated with the Drift AI chat agent, accessible via Salesloft, to gain unauthorized access to Salesforce customer instances. This systematic campaign led to the exfiltration of sensitive data, including AWS access keys, passwords, and Snowflake tokens, from over 700 organizations, indicating a potential supply chain attack.

Lenovo's GPT-4-powered chatbot "Lena" was vulnerable to cross-site scripting (XSS) attacks due to improper input and output sanitization, initiated by a malicious prompt. This allowed attackers to steal session cookies and potentially gain unauthorized access to customer support systems, facilitating further system command execution and lateral movement.

A remotely exploitable zero-day vulnerability, CVE-2025-37899, has been discovered in the Linux kernel's Server Message Block (SMB) protocol using OpenAI's o3 model. This critical flaw is identified as a use-after-free bug in the SMB 'logoff' command handler, allowing an object to be freed while still accessible by another thread.