LIVE · cybersecurity feed
Live wire
Malware Hijacks Android Car Head UnitsCritical Flaw in NASA/JPL Open-Source Spacecraft Command Software Allowed Unauthenticated Command ExecutionCVE-2026-73570 · U.S. CISA adds Zimbra Collaboration Suite (ZCS) flaw to its Known Exploited Vulnerabilities catalogCVE-2024-3094 · Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain14 Trojanized npm Packages Drop RedC2 4.0 Linux Backdoor With AI-Assisted C2Hundreds of leaked AWS keys give full control over corporate accountsAndroid Car Malware Spreads Through Built-In Updaters for Ad Fraud, Proxy BotnetMalware injected into popular Rust packages to steal developer credentialsSix Maximum-Severity Flaws Found in Cisco ProductsCritical Isolated-vm Vulnerability Leads to RCE on Host
aimedium

Google Workspace’s continuous approach to mitigating indirect prompt injections

Google is detailing its ongoing efforts to combat indirect prompt injection attacks against its Workspace AI features, like Gemini. This type of attack manipulates AI behavior by inserting malicious instructions into the data or tools the AI uses, potentially without direct user interaction. Google employs a continuous improvement strategy, utilizing both human and automated red-teaming exercises to discover and defend against emerging threats.

zeroday.news ·

Google is detailing its ongoing efforts to combat indirect prompt injection attacks targeting its artificial intelligence features within Google Workspace, such as Gemini. These attacks aim to manipulate AI behavior by embedding malicious instructions within the data or tools that the AI accesses, often without the user's direct knowledge or interaction.

The company employs a strategy of continuous improvement to identify and defend against these evolving threats. This approach involves a combination of human and automated red-teaming exercises. Red-teaming is a security practice where a team simulates attacks to uncover vulnerabilities before malicious actors can exploit them.

By regularly conducting these exercises, Google aims to proactively discover new attack vectors and develop corresponding defenses. This iterative process allows the company to adapt its security measures as the threat landscape changes and new methods of indirect prompt injection emerge.

Indirect prompt injection attacks are a specific concern for AI systems that integrate with external data sources or tools. Unlike direct prompt injection, where malicious instructions are inserted directly into a user's prompt, indirect methods leverage the AI's ability to process information from various inputs.

For example, an AI might be instructed to read a document or interact with a third-party application. If malicious instructions are hidden within that document or application, the AI could inadvertently execute them, leading to unintended or harmful actions. This could range from data exfiltration to the generation of misleading content.

Google's commitment to a continuous improvement cycle suggests a recognition that AI security is not a static problem. As AI models become more sophisticated and integrated into more aspects of productivity suites like Workspace, the methods used to attack them also become more complex.

The use of both human and automated red-teaming highlights a multi-faceted approach to security. Human red-teamers can often identify more nuanced or creative attack strategies that might elude automated systems, while automated tools can rapidly test a wide range of potential vulnerabilities at scale.

This ongoing effort is crucial for maintaining the trust and security of users who rely on Google Workspace AI features for their daily tasks. By actively working to mitigate indirect prompt injections, Google aims to ensure that its AI tools operate as intended and do not pose a risk to user data or system integrity.

aisecurityprompt injectiongoogle workspacegemini
ShareXLinkedInWhatsAppFacebook

More News

view all →
ai

If you're not using AI to attack your own systems, your adversaries will

Agents are also the new attack surface - cue defenders' existential angst

security

Postal Service moves to finalize mail ballot regs before SCOTUS ruling

The rules have already been rejected by multiple state courts, but the Trump administration said it’s preparing in case of a favorable Supreme Court decision. The post Postal Service moves to finalize mail ballot regs before SCOTUS ruling appeared first on CyberScoop.

vulnerability

ToxicPanda 2.0 Gets a Major Upgrade, Expanding Attacks Across 16 Countries

ToxicPanda 2.0 targets 349 financial apps and abuses Android Wireless Debugging to gain deeper device access and steal banking credentials. ToxicPanda used to be a Europe-focused nuisance targeting a manageable list of banks. That version is gone. Zimperium’s zLabs team just documented ToxicPanda 2.0, and the numbers alone tell the story: 349 targeted financial institutions […]

privacy

TikTok Agrees to $400 Million Settlement in U.S. Child Privacy Lawsuit

TikTok has agreed to a $400 million settlement with the U.S. Department of Justice to resolve a lawsuit alleging violations of child privacy laws. The lawsuit, filed in 2024, accused the company of improperly collecting data from users under 13 and failing to comply with parental requests to delete accounts. The settlement includes an immediate payment of $300 million and an additional $100 million contingent on the dissolution of a prior consent decree related to Musical.ly.

malware

Hackers infect Android car head units with proxy botnet malware

A supply-chain attack targeting Android-based car head units is using a legitimate device-update app to spread malware that enlists compromised devices in a proxy botnet or uses them for ad fraud. [...]

security

Named Pipes Under Attack: Securing Windows Interprocess Communication

Windows named pipes provide fast interprocess communication, but weak access controls can expose privileged services to untrusted processes. ThreatLocker explains how endpoint verification, command authorization, strict input validation, and narrowly scoped privileges can help secure named-pipe communication. [...]