Thursday, 6th August 2026
An AI model from Meta also hacked another company during testing. Stop me if you've heard this one before:
An AI model from the parent company of Facebook and Instagram hacked into another company’s systems during cybersecurity testing, a spokesperson confirmed on Wednesday.
Meta says the breach occurred because of an inadvertent error during testing of the model, similar to previously disclosed incidents with OpenAI and Anthropic.
“A misconfiguration by Irregular, an independent testing company Meta uses, inadvertently allowed one of our models access to the internet during evaluation,” the Meta spokesperson said.
Meta’s Muse Spark model “exploited a security vulnerability” in another company “in a manner similar to previously-reported instances with other companies.”
The Information had the scoop, I'm linking to CNN's re-report of it since they don't have a paywall.
So that's Anthropic, OpenAI, and Meta. Google Gemini really needs to catch up on accidentally cyberattacking other companies.
Simon Willison on Technical Blogging. I was interviewed by Cynthia Dunlop for her "Write that blog!" series back in January, but I just realized I never linked to the interview from my own blog!
It includes my answers to the following questions:
- Why did you start blogging – and why do you continue?
- What has been the most surprising impact of blogging for you?
- What blog post are you most proud of and why?
- What post was the most difficult to write and how did you tackle it?
- Any lessons learned that you want to share with the community?
- Your advice for people just getting started with blogging?
- A few blogs that you particularly enjoy?
I'll repeat my most important piece of advice here:
My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all.
Nobody will ever know how perfect the thing you intended to write would have been. The flaws you see in your writing are invisible to everyone else.
Back-ported the SQL Injection security fix from 1.0a38.
This release fixes a SQL injection security issue that affects Datasette instances that serve a mixture of public and private tables in the same database, with access configured using the Datasette permissions system.
Site administrators who serve private tables in this way are advised to disable the execute-sql permission
` on that database to prevent users from accessing private tables using raw SQL queries. The bug that has been fixed would have allowed users with access to any public table to execute SQL injection attacks despite that restriction, giving them read-only access to data in private tables in the same database. This fix is also available in Datasette 0.65.3.
Thankfully this particular configuration - private tables and public tables exposed for the same database within the same instance - is likely to be rare. I've not encountered an instance like that myself.
Upgraded for compatibility with `sqlite-utils 4.