> daily_signal(2026_11_11)

AI coding tools backed out of reverse engineering, a breach spilled an inference provider's keys, Amazon built a drone to patrol your home, and a free offline model cleaned medical records.

PickBits Daily Signal · Wednesday, November 11, 2026

By Mark Pickering · 8 min read · November 11, 2026

// tl;dr

Three of today's four stories rhyme, and not in a way I love. Claude Code and Codex stopped letting people take apart hardware they own. Fireworks AI leaked the keys that thousands of companies trusted it to hold. And Amazon built a camera that flies through your house and phones home to its cloud. We've watched vendor policies tighten for months, so none of this came out of nowhere. This week it landed on three different groups at once, and none of them were the ones running the AI.

The fourth story goes the other way, and it's the one I'd bet on. A few researchers gave away an AI that scrubs patient records clean and never sends a byte to the cloud; it runs on the hospital's own box. That's the version of this I actually want. You download it, you run it, nobody else gets a vote. I'd take a lot more weeks that end on that story.

Decomp.wtf went dark this week, and the reverse-engineers who kept it running moved to models they can run without asking permission.

1. The two biggest AI coding assistants are quietly backing out of reverse engineering.

Claude Code's safety checks block decompilation, and OpenAI has throttled Codex accounts under cyber-abuse rules. The people who did this work are leaving for open-weight models that answer to no usage policy.

People have been using AI to take gadgets apart and see how they work. This week two things cut that off at once. Claude Code's new "safety checks" started refusing to help with decompilation and reverse engineering, and OpenAI suspended or limited Codex accounts under "cyber abuse" rules. One r/ClaudeCode regular put it flatly: "The Dream is dead." OpenAI's Tarun Gogineni says the Codex blocks are "mostly accidental," that there is "no prohibition against reverse engineering with Codex," and that a fix is on the way.

And it's not only coders who should care. This is the same fight as right-to-repair: whether a company gets to decide what you can do with a device you bought. But a usage policy isn't a law and doesn't have to be. The model just declines, with no appeal and no record anyone can point to. The Decomp.wtf game-decompilation project has already shut down, and a Cornell Tech, Columbia, and NYU paper (arXiv:2611.10433) is now mapping where copyright and reverse-engineering law actually stand. The community's response has been to stop asking permission, moving to open-weight local models like GLM-5.3 that run on their own machines with no policy in the loop at all.

Screenshot of 404 Media's November 10 report on AI companies blocking AI-assisted reverse engineering.
404media.co · November 10, 2026

Why this matters: So the chatbot just says no, and there's nobody to appeal to. A model that won't explain how your own router firmware works is making a legal-looking call with none of the process a law would need, and OpenAI calling its Codex blocks "mostly accidental" tells you the line was never deliberately drawn. We've watched vendor usage policies tighten all year, from models pulled offline over security to access locked down "for safety." This week it hit people who were just taking apart gear they paid for.

Action this week: Pull down one open-weight model and run a reverse-engineering question through it locally before you need to, because GLM-5.3 and its peers do this work with no usage policy attached. My own read is that the vendors will keep the "accidental" blocks and quietly widen them, so the fix that lasts is owning the model yourself; a cleverer prompt won't do it. If you build on a hosted coding agent at work, get it in writing which categories of request it will refuse, because "mostly accidental" isn't a service guarantee.

404media.co: Reverse Engineer Anything: AI Companies Crack Down on the Coolest Thing People Were Doing With AI (November 10, 2026)
arxiv.org: AI-assisted reverse engineering and intellectual-property law (arXiv:2611.10433v1, Cornell Tech / Columbia / NYU)

2. Fireworks AI was breached twice in October and lost its "secrets."

The inference provider serves more than 10,000 companies. Those "secrets" are the credentials that unlock customer accounts, and Notion has already cut Fireworks off and deleted the data it held there.

If your company's stack calls a hosted AI model, and most now do, the vendor-security review you keep meaning to run just got specific. Fireworks AI, an inference provider with more than 10,000 customers, disclosed two breaches in October: an October 6 intrusion by a financially motivated group, and an October 23-24 compromise of a third-party cloud provider that hosted its research machines. The stolen material includes account and billing information, invoices, internal datasets, and what the company calls "secrets," meaning credentials that grant access to users or apps. Palo Alto Networks' Unit 42 is investigating.

Watch what Fireworks' own customers did. Notion disconnected from the service on November 2, deleted the data Fireworks held for it, and switched off its Insights feature rather than wait for the all-clear. Fireworks ties the incident to LLMjacking, the racket we have tracked since October where stolen AI keys get used to run up enormous model bills on someone else's account. Google's Mandiant has seen fraudulent charges top $100,000 in a single day and reach $1 million cumulatively at some organizations before anyone noticed. A breach that spills "secrets" is where those stolen keys come from.

Screenshot of The Record's report on the two October breaches at inference provider Fireworks AI.
therecord.media · November 10, 2026

Why this matters: Your model keys may already be in a breach you will never be named in. The companies most exposed here did nothing wrong except pick a vendor, and the first sign of trouble is usually a bill landing rather than an alert firing, because Mandiant's six-figure days show up before the fraud team looks. We flagged in October that stolen keys were quietly funding autonomous scanning; this is where those keys come from.

Action this week: Rotate every credential that touches a hosted inference provider, starting with Fireworks if you use it, and put a hard spend cap and an anomaly alert on each one. The spend cap is the part people skip and the part that actually stops a $100,000 day. Then ask each AI vendor, in writing, two plain questions: where do you store customer "secrets," and how fast will you tell me if they leak. If the answer's vague, that's your answer, and forward it to whoever signs off on your vendors.

therecord.media: AI company Fireworks says hackers stole data in October attacks (November 10, 2026)

3. Amazon's Ring is shipping a $249.99 AI drone that flies around inside your home on its own.

It launches January 27 as the Ring Drone Cam, patrolling preset routes when a sensor trips. The never-shipped Always Home Cam idea, six years late, finally flies.

Ring, Amazon's home-security arm, will ship the Ring Drone Cam on January 27, 2027 for $249.99. Founder Jamie Siminoff announced it at a New York launch event, nearly six years after Ring first teased, then shelved, the Always Home Cam. This is that idea made real: a small indoor drone that reacts to a Ring sensor (motion, a door opening, a water leak, an alarm) by flying a preprogrammed route to a set spot, livestreaming and recording 2K video to the Ring app. It can also run scheduled patrols or launch on demand while you're out.

There's no settled rulebook yet for a camera that flies through your living room and streams what it sees to Amazon's cloud. For most buyers, the only real gate is whether you click buy. We've been skeptical of Ring's privacy story for a while, and in September we argued that its "throw away the key" encryption still didn't deliver the privacy the marketing promised. A flying camera makes all of that a lot harder to shrug off, and it raises a question a doorbell never did: once that footage is sitting on Amazon's servers, who gets to pull it later, with a subpoena or without one.

Screenshot of The Verge's hands-on with Amazon Ring's $249.99 flying Drone Cam.
theverge.com · November 10, 2026

Why this matters: A doorbell camera watches your porch. This one watches your living room, and everything it records lands on Amazon's servers, not yours. The convenience here is real, I'll give it that. A live view of a tripped alarm from three states away is genuinely handy, which is also what gets you to click buy without reading what happens to the footage. My own read: the tech was never the problem. We just keep buying the next camera for the next room in.

Action this week: Set the house rules now: where it's allowed to fly, who gets told it's there, and whether it ever patrols when someone is home. Write them down now, because the minute you can launch it from your phone, those rules are the first thing to slide. And read Ring's data-retention and law-enforcement-request terms before you buy rather than after. Where the footage ends up is the kind of thing you want settled before you hit record.

theverge.com: Ring Drone Cam hands-on: price, release date, and the AI that flies it (November 10, 2026)

Listen to the Daily Signal podcast at pickbits.ai/daily-signal.

4. Researchers open-sourced a free AI that strips patient names from medical notes without the data leaving the building.

Called DeidSharp, it runs on a hospital's own hardware and caught 98.9% of private details on test records, beating the standard tools by more than 20 points of recall.

This one is built for the patient whose nursing notes get handed to a research team, and for the small hospital that wants to share records for a study but has no cloud budget and can't take on the risk. DeidSharp, a free, open-source toolkit released November 9 (arXiv:2611.12709, with code on GitHub), is built for exactly them. It removes personal health information from clinical text using a locally hosted 26-billion-parameter model alongside plain pattern rules and a clinical name-detector, and it "fails closed": on any detector error it redacts rather than risk a leak. Because every piece runs on-site, the notes never leave the building.

And the numbers are real. On PhysioNet nursing notes it caught 98.9% of private details, and on MIMIC-IV discharge summaries it beat the widely used Stanford and Penn de-identifier by more than 20 points of recall. We've seen this a few times lately, from Alibaba open-sourcing a medical model in September to offline clinical-literature search in October: capable AI that doesn't send a patient's records off to some data center. The authors flag the catch themselves. A self-verification step discarded about a quarter of the private details it had correctly found, so some real names slip back through, and that gap is the number the next version has to close.

Screenshot of the arXiv paper introducing DeidSharp, a free local clinical de-identification toolkit.
arxiv.org · November 9, 2026

Why this matters: With medical AI you usually have to choose between making records useful and keeping them private, and the patient rarely gets asked which. We've made that point before, back when the research showed the privacy risk lands hardest on the most vulnerable patients. DeidSharp goes the other way. The code is free, it runs where the data already sits, and nothing leaves the building. You don't have to take a vendor's cloud on faith; you can read the code and run it yourself.

Action this week: If you handle clinical text, put DeidSharp on a locked-down test box and run it against your own records before you believe any benchmark, including this one. I'd watch the recall-first setting specifically, because that quarter of discarded detections is where a real name leaks, and a de-identifier that fails silently is worse than none. And the part I actually like: a hospital can run a tool like this itself now, instead of renting it from a cloud it can't see into.

arxiv.org: DeidSharp, an open-source toolkit for local de-identification of clinical text (arXiv:2611.12709v1, November 9, 2026)
github.com/valburkin/DeidSharp: source code (.NET, CC BY 4.0)

» What to watch this week

Tomorrow's signal lands here.