Google DeepMind’s paper shows that the real security problem for AI agents is not just the model, but the environment it reads. Presents the first systematic framework for understanding how the web itself can be weaponized against autonomous AI agents. As agents increasingly browse the internet, read emails, execute transactions, and spawn sub-agents, the information environment becomes an attack surface. In one cited benchmark, hidden prompt injections embedded in web content partially commandeered agents in up to 86% of scenarios, sub-agent hijacking working 58–90% of the time, and data exfiltration attacks clearing 80% across five different agent architectures. That reframes the whole debate. We usually talk about model safety as if the danger sits inside the weights, but agents do something more fragile: they browse, retrieve, remember, and act on untrusted material in real time. The paper’s key contribution is a taxonomy of “AI Agent Traps,” six attack classes aimed at perception, reasoning, memory and learning, action, multi-agent dynamics, and even the human overseer. Here’s the key point. A web page does not have to look malicious to be dangerous to an agent, because the agent may parse what humans never see: hidden HTML comments, metadata, CSS-hidden text, formatting syntax, or adversarial content embedded in images and other media. The threat gets more serious once memory enters the loop. If an agent uses RAG or persistent memory, poisoning no longer has to win in one shot. It can sit quietly in a corpus or memory store and activate later, which is why the paper highlights results showing latent memory poisoning above 80% attack success with less than 0.1% data contamination. What makes this paper useful is its restraint. It does not pretend every category is equally mature. Content injection and behavioural control already look concrete, while systemic and human-in-the-loop traps are presented more as an emerging research frontier than a solved empirical case. The larger point is hard to ignore: once agents are allowed to ingest the open web at inference time, every page, document, and memory write becomes part of the security boundary. --- ssrn .com/sol3/papers.cfm?abstract_id=6372438

Google CEO Sundar Pichai on current frontier model's ability to break the security of almost all current software. "These models are definitely, like really gonna break pretty much all software out there, maybe already, we don't know."

Google Drive Is Not a Backup: Here's What Actually Works Most people assume Google Drive is a backup solution. It's not. It's a sync tool. If your computer gets hit by ransomware, the encrypted files will sync straight to Google Drive. If you accidentally delete something, Google Drive deletes it too. That's how sync works, it mirrors whatever happens on your machine. So if your data actually matters, don't keep it in just one place. The most reliable setup is straightforward: Local computer → NAS → Cloud backup One copy on-site, one copy offsite. If your computer dies, you accidentally delete files, or your account gets compromised, you can still recover everything. Paid tools worth considering: •Synology: The go-to for home and business NAS. Mature, reliable ecosystem. •Backblaze: Affordable, with excellent automation. Great for set-and-forget backups. •Acronis: Enterprise-grade backup with strong recovery options. •Wasabi: Cheap cloud object storage with no egress fees. •Dropbox Business: Solid for team collaboration, though keep in mind it's primarily a sync tool, not a true backup. Open-source alternatives: •rclone: Incredibly versatile. Syncs and backs up to dozens of cloud providers. •Restic: Lightweight, fast, with built-in encryption and deduplication. •BorgBackup: Popular in the Linux community. Excellent compression and deduplication. •TrueNAS: The standard for self-hosted NAS builds. •MinIO: S3-compatible private object storage. Great for self-hosted setups. Most serious tech teams eventually land on the same architecture Because storage isn't the hard part. Recovery is: Local NAS + cloud object storage + versioned backups The real question isn't "where is my data stored?" It's "can I get it back when something goes wrong?" This is the A part of the “CIA” triangle. #cybersecurity#

Google uses Python. Meta uses Python. Netflix uses Python. Spotify uses Python. Dropbox uses Python. Instagram uses Python. Reddit uses Python. Uber uses Python. Pinterest uses Python. OpenAI uses Python. What’s stopping you from learning Python?

Google's advocacy news today is is trying to get Sen. Bill Cassidy of Louisiana re-elected. Even Fox News story has a "positive" re-election story - supporting Cassidy. Why would this story rise to the headline news? Most likely this is pay-for-play. This is big pharma meddling in MSM again. Yes, they pay MSM big $$$ to run advocacy pieces - written by pharma ghost writers. The man has been a disaster. He has opposed MAHA at every turn, voted for Trump's impeachment and done very little positive for Louisiana. It is only because Louisiana had a jungle primary and democrats could vote for him, that he got elected to the Senate in the first place. Gov. Landry got rid of that nonsense. Now only Republicans can vote in the Republican primary. Cassidy is a RINO - who supports democrats more often than not. His votes in the Senate often support democrats on institutional, health-care, and bipartisan governance issues. Woke issues. He needs to be voted out of office. Julia Letlow is now polling way ahead of Cassidy. She is not a perfect solution, but she is way better than Cassidy. She needs our support.