Lucc @securitystack

Had fun writing this talk for our MPhil students today: "How to avoid AI Brain Rot" Discussing how to avoid intelligence atrophy from AI use in work and study. And how to stand out on an ever-narrowing bell curve

Here is the full talk:

Miles Cranmer @MilesCranmer

3 days ago

Had fun writing this talk for our MPhil students today: "How to avoid AI Brain Rot" Discussing how to avoid intelligence atrophy from AI use in work and study. And how to stand out on an ever-narrowing bell curve

20 69 1K 379K 1K

My prediction: we’re heading toward software that continuously rewrites itself and adapts to the person using it. Agents will increasingly improve applications and parts of their own code. Making that secure will require strict sandboxes, least privilege, and security controls the agents can’t modify themselves. A trusted authorization service should issue narrowly scoped, short-lived OAuth access tokens for specific resources and actions. UI, workflow, and eventually more backend logic could change based on each user’s needs and behavior. Humans will soon stop manually reviewing every change. We’ll need automated testing, independent security checks, a record of exactly what ran, and reliable rollback. I expect this to shake up both open source and proprietary software. The ability to inspect, modify, and share software will still matter. But more of our work will shift toward defining requirements, controlling access, and verifying applications that agents keep changing. That is a much bigger shift than simply having AI write our code.

VirusTotal is now available in ChatGPT Scan files, URLs, and domains for potential threats, right from your chat chatgpt.com/plugins/plugin…

Anthropic released code-modernization v1.0.0, a Claude Code plugin for modernizing legacy codebases Save this post if you have a legacy project worth modernizing What I find interesting is that it doesn’t just rewrite code. It tries to prove the new implementation behaves like the original Here’s how: - Analyzes the legacy system and extracts business rules - Generates a modernization plan for your approval - Rewrites or upgrades the code, even across languages - Runs the old and new implementations with identical inputs and compares outputs - Generates additional edge cases to test behavior - Introduces deliberate bugs to verify tests actually catch them - Produces a verification report with PROVEN, PARTLY PROVEN, or NOT PROVEN results It also keeps the original code untouched and requires human approval at critical steps I think this is the right direction for AI-assisted modernization, generating new code is one thing Proving that you haven’t broken existing behavior is a completely different challenge Install:
/plugin install code-modernization@claude-plugins-official Repo:
github.com/anthropics/cla…

there is zero reason to use python in 2026 it's inferior in every single way and the only benefit it ever had (ease of use) is completely meaningless now that agents can write all the code

For the second time in Google Chrome’s history, Google awarded a $250,000 bounty for a full-chain exploit… to @XBOW. Here’s the full story: At an all-hands at the start of 2026 in Malta, I set the team a crazy challenge. A full-chain exploit of Chrome by the annual Black Hat cybersecurity conference in August. I believed there were few better tests of whether @XBOW could move beyond web applications to desktop software, servers and devices. Chrome is one of the most hardened pieces of software on the planet, used by more than half the world’s population. A full-chain exploit lets an attacker take total control of a machine, where they can read every email, password and bank login the user types. You don’t need to download anything or click a phishing link. Visiting the wrong site is enough. So @moyix, Andres Luksenberg, Baul Lee, and Willem Pinckaers took on the challenge along with a fifth teammate: OpenAI's GPT-5.6 Sol. They built a chain they thought would win, but Google told us they already knew one of the bugs. We were already in Las Vegas for Black Hat and DEF CON, and the team didn’t want to go home without the win. So Brendan and the agents built a new exploit in just 6 days. We submitted it to Google and waited. The news came through that we'd done what should’ve been impossible. A full-chain bounty of $250,000, the first awarded under Google’s 2026 rules. It took just 6 days and $40,000 of compute to construct an exploit that affects a billion users of Chrome on Windows. An intelligence-agency veteran told me his team used to spend 6 months on this kind of vulnerability. My takeaway: the cost of finding truly critical vulnerabilities is collapsing, for attackers and defenders alike. Restricting powerful models is not the answer; GPT-5.6 Sol is already public. But defenders have one advantage attackers never will: they can test their own code first. Assume your software is exploitable. Whoever is hunting your bugs has the same building blocks we did. This is cause for urgency but not panic. XBOW is now developing an autonomous product for testing compiled software (desktop applications, servers, embedded devices), and partnering with the world’s top organizations to design that product. If you’d like to be one of them, get in touch. P.S. Restart Chrome whenever the Update button appears!

We were able to fine tune an open weight model (Qwen3.5-9B) on proprietary internal data at @coinbase, and it out performed frontier models, at much lower cost and speed, for a specialized task (fraud prevention in this case). I think we'll see more of this pattern inside companies. The frontier models are amazing generalists. But increasingly you'll see specialist models out perform on more narrow tasks, either working on teams, or by themselves. We're making it easy to fine tune models internally for our employees. We even have a skill for it in our internal harness that makes it easy to spin these up and start training them: "/fine-tune-and-serve-llm I want to fine-tune Qwen for payments risk review. help me get started" I imagine we'll have some backend services that could be replaced entirely by this new architecture.

keyboard_arrow_left Previous keyboard_arrow_right Next

REA（Reverse Engineer Anything）逆向一切 三天从 3 万 Star 涨到 12 万+，一天新增 2.5 万以上。MIT 开源。 大家都在说它，"一切软件都可逆"， 我看到更好玩的是：拆硬件的通信协议。 家里的空调、热水器、灯，基本都配了一个难用的厂商 App。App 背后，其实就是一套设备通信协议。 REA 这几天的更新正好补齐了这条链路： · adb 连模拟器或真机，抓到官方 App · 分析 HAR 或 mitmproxy 抓包，把每个请求定位到 App 源码 · 用 Binwalk/Unblob 拆固件，再交给 Ghidra 分析 然后把证据交给 Claude Code / Codex，还原协议，自己写控制端。 X 上已经有人用同样的思路，逆向了空调，做成 Mac 状态栏应用，又花 15 分钟移植到 AR 眼镜上，看一眼就能控制。 以前是厂商 App 决定你能怎么用自己的设备，以后你可以自己写。 x.com/icanberk/statu…

China has killed the entire vector database industry. They open-sourced TencentDB Agent Memory. It gives any AI agent long-term memory that runs 100% locally. No Pinecone. No cloud APIs. No repeating yourself every session. - 61% fewer tokens - PersonaMem accuracy: 48% → 76% - Zero external API dependencies - Runs on plain SQLite Most memory systems compress your history into an opaque vector pile. when recall goes wrong, you're guessing. this one doesn't compress, it builds a semantic pyramid. L0 Conversation → L1 Atom → L2 Scenario → L3 Persona. Short-term state gets encoded as a Mermaid graph in your agent's context. verbose tool logs get offloaded to disk. when the agent needs proof, it drills back via node_id to the exact raw log. no lossy compression. every layer is readable markdown you can just open and inspect. 5.1k stars. 100% Open Source.

Excited to share a research blog post that Daniel Freeman (@bucketofkets) and I have been working on for the past few months: anthropic.com/research/self-…

The teaser for the new LifeOS 8.x release! share.danielmiessler.com/VyYP1juczT/raw

Software as we know it is coming to an end. The traditional model of open-source and closed-source software, built and maintained by large, expensive engineering teams, will fundamentally change over the next few years. Even the tools we use to build software today will become increasingly obsolete. What replaces all of this? AI-native, personalized software that is dynamically created, continuously evolves, and adapts to each user’s unique needs, preferences, and behavior. We are moving from software built for millions of users to software built for the individual.

@kmad @matthew_pines I think we might lose public key cryptography.

Claude Dashboards and Claude Motion are in beta today. Ask Claude to turn your data into live dashboards and your ideas into animated explainers.

Through The Mission (launching today), we'll release research, tools, and resources to help secure the world. Two programs: 1/ OSS Scanner, inspired by OSS Fuzz, for maintainers to receive more bug reports/pocs/fixes faster and 2/ the Critical Infrastructure Defense Program, where we will work with critical infrastructure providers to figure out what works then scale them up. Backed by our own research and engineers. Think of the Mission as the ~complement to our model access. We recently expanded cyber access this wk via our new CVP. But we need to make it really easy to find & fix everything, but also rewrite software/systems, especially for critical infrastructure. Our sense is we've got a ~few years to transform security. That's going to take require a fast feedback loop that brings AGI cybersecurity research into the world. We've built a very cool team, led by @benhawkes, and then we'll scale our work as we learn what works.

Anthropic @AnthropicAI

a week ago

We’re launching the Anthropic Cyber Mission, a new effort to secure critical infrastructure and open-source software. anthropic.com/news/anthropic…

276 293 3K 346K 604

We’re launching the Anthropic Cyber Mission, a new effort to secure critical infrastructure and open-source software. anthropic.com/news/anthropic…

Cyber is having a moment Across 21 major software companies, including Apple, AWS, Microsoft, and Google: - Reported critical vulnerabilities never cleared 100 per month in four years - Since spring they've jumped to over 600 per month

a16z @a16z

2 weeks ago

Kevin Mandia on finding 90+ security holes at Fortune 500 companies that nobody knew existed: "When you have an AI-based attack, it'll find logic flaws rather than code flaws in custom applications. It'll exhaust all routes all the time." "Armadin, since January of this year,

20 18 127 114K 76

quincunx33/ai-jailbreak: A collection of jailbreak prompts and exploit techniques for local and frontier AI models, with modern methods for Qwen3.5, Gemma 4, Llama 4, Kimi K3, GPT-OSS, GPT-5.x, Gemini 3.x and Grok 4.x. For red-... github.com/Quincunx33/Ai-…

This is the doom I predicted a few days ago, coming for Photoshop. A clean-room open-source reimplementation. No prizes for guessing that they decompiled Photoshop to source code, processed that to some kind of non-code specification language, then fed the spec to an LLM with an instruction to generate Rust. Adobe just got nuked. And closed source is dead, dead, dead. github.com/storytold/phot…