This article (2026/June) review and compare 39+ #AI-assisted OpenSource #Pentesting Tools: 6 distinct architecture patterns: single-agent, multi-agent planner-executor, specialized roles, swarm, MCP-based, and Claude Code native.🔥🤖
appsecsanta.com/research/ai-…
🪶Chilcano retweeted
Losing battle imo: no software system is hermetically sealed.
You can keep burning $ finding vulnerabilities, you will never find them all, you’ll never test every combination of variables & deployment nuances & stacks.
The only worthwhile investment is in how we design & ship
Our security researchers built an autonomous cyber vulnerability discovery, exploitation, and patching pipeline.
In a single run with an upcoming cyber model, it validated and generated patches for 948 local privilege escalation vulnerabilities in the Linux kernel at a total API cost of $1.2 million.
🪶Chilcano retweeted
> be AI company
> scrape the entire internet
> ignore licenses and copyright
> download millions of pirated books
> use them to train frontier models
> spend tens of millions buying physical books
> cut off their spines
> scan every page
> destroy the originals
> lecture everyone else about intellectual property
> we are the good guys
Replying to @chasmmmmmmmmmmm
We added two sentences to Claude Code's prompt on Opus 5.5 to steer it away from recreating someone else's specific game because using Claude to infringe IP is against our usage policy.
Original games, genre games, and games built from your own designs and assets are meant to keep working.
We'll continue to iterate to ensure we're striking the right balance. In the meantime, if Claude turns down something that's yours, send it my way.
🪶Chilcano retweeted
my spidey senses are telling me the labs are, as we speak, using unguardrailed versions of their unreleased models to systematically reverse-engineer ALL of the internet’s software, apps, and games, then feeding the reconstructed source code straight into their training pipelines while simultaneously building guardrails to ladder-pull the rest of us
🪶Chilcano retweeted
A developer who writes a fork of ARTEX messaged me today to call me very naughty name for releasing spikestrip
He didn’t have the dev chops to fix ARTEX to think hard enough to not honor the traps.
github.com/Arcanum-Sec/Spike…
🪶Chilcano retweeted
Today @_rybaz and I are publicly releasing all the materials for our Introduction to Harness Engineering for Vulnerability Research training we gave at @unpromptedconf last week.
Our goal was to teach the concepts we've been using to do much deeper security research and make both vulnerability analysis and red team engagements far more impactful.
The workshop can be found here: grahamhelton.github.io/harne…
The slides can be found here: grahamhelton.com/talks/2026-…
Announce kmorph: Kernel Live Update, No Reboot Required
Kernel CVEs are piling up faster than we can patch them, and the reboot is what's holding us back.
AI tools are finding kernel bugs faster than ever. Live patching can't keep up: each patch is written by hand and only covers small function-level fixes. Everything else waits for a full kernel update, and that still means a reboot, which is so costly across a fleet that teams update far less often than they should.
So we set out to get rid of the reboot.
kmorph, now under testing, moves a running Linux machine to a new kernel with no reboot at all. On a multikernel machine, the new kernel boots ahead of time on its own CPUs and memory, beside the running one. When it is time to switch, it fences the old kernel's CPUs, adopts its CPUs, memory and devices, and keeps the machine running. About one second, and no kernel boots in the critical path.
The same takeover handles crashes: if the old kernel panics, the new one takes over on its own.
How is this different from upstream LUO (Live Update Orchestrator)? LUO preserves selected state across an update, but underneath it is still a kexec reboot: the old kernel stops, then the new one boots from zero. A faster reboot is still a reboot. With kmorph, the new kernel has already finished booting before it is needed, and it can take over even when the old kernel is dead.
We are looking for early testers and contributors. If kernel updates cost your fleet capacity, SLAs or sleep, try it, file issues, send patches, or just tell us what you need.
github.com/multikernel/kmorp…
#Linux #LinuxKernel #LiveUpdate #Multikernel #SRE
🪶Chilcano retweeted
Excellent comment on this FT article about the Binance hack
ft.com/content/1d4dd7b2-9dee…
🪶Chilcano retweeted
New VOLTA Infostealer Uses Claude, Gemini, and Kimi AI to Rank Victims by Financial Value thehackernews.com/2026/11/ne…
🪶Chilcano retweeted
Binance hack: compromised devops employee laptop
Polymarket hack: compromised third party vendor
What is “patch the planet” doing here?
regarding cve-2026-98432: it is a uaf in tcp, mptcp is needed to make the race win and to get the leak and write.
the impact of the bug is bad, its essentially go2shell, caddy2shell etc. go 1.24+ servers are all vulnerable, because mptcp is enabled by default.
BUT:
1. It is extremely hard to win the race reliably, anthropic said it took 40 mins for them to get leak and defeat kaslr
2. It is probably hard to exploit in practice. most routers, lbs and isps drop ip options, without that header you can't race at all, so realistically only a same network attacker can try, which is pretty common in sandbox infra
my mythos worked on this for last 3 days burned ~$2k and couldn't build a reliable poc that can be sprayable. gpt-5.6 sol als exhausted my subscription and couldn't even get a leak.
either anthropic has a unreleased model which is better than their public one or they have a pro exploit dev internally.
🪶Chilcano retweeted
Idiot Binance hackers compromising a developer machine. Don’t they realize they could be spraying php2shell attacks instead? I guess they suck at writing exploits.
🪶Chilcano retweeted
A new initiative proposes independent security audits and formal verification of the EEZ smart contracts.
The goal is to strengthen the security and reliability of EEZ through independent review and transparent verification.
initiatives.thedao.fund/init…
🪶Chilcano retweeted
To all of my pentesting friends. What cyber model actually helps you do black box pentesting and similar without being blocked all the time?
Most of my pentesting friends tell me that they’re getting blocked on a regular basis regardless of what model they’re using.
Anybody have a different story?
🪶Chilcano retweeted
Why are the AI labs releasing cyber models?
1. There’s a lot of $ to be made
2. We’ve had extremely smart people make use of AI for security, setting a precedent, paving the path early
There are other niches where this will apply, but few have both of these attributes.
The problem with huge financial incentives, is they bring lies, deceit, sales psychopaths & charlatans exploiting the situation.
As cybersecurity practitioners, it is very important for us to prevent their attempts to control our tools.
We need to focus on self-hosted models, cheap alternatives, open-source models, and any way to decentralize tools and prevent big ai labs from monopolizing tooling.
Cybersecurity tools for everyone, no guardrails, no KYC checks, no account managers or “contact sales” buttons
🪶Chilcano retweeted
Introducing the "Grim Prompter" one of the largest collection of open source threat modeling prompts on the planet. 😎
I built Grim Prompter to help developers threat model with Claude Code, Codex, or any coding agent. 36 architecture workflows and 29 method and analysis prompts!
MIT licensed. Use it, improve it, share it. Security tools should help everyone.
github.com/jmanico/grim-prom…
⚠️🚨 you all need to patch brotli2shell/http2shell!⚠️🚨
we keep finding vulnerable versions in production during our client red teaming engagements. these bugs are usually at the application level, so most of your monitoring won't even catch them, and the impact could be whatever matters most to your organization.
🪶Chilcano retweeted
This is an impressive amount of FUD built around an AI agent that was given a detection engineering task.
Cohere asked the model to write a detection rule for curl-based malware delivery. Anyone with practical experience in detection engineering knows that writing a rule is only part of the job.
You examine the environment, generate or collect relevant telemetry, inspect the resulting events, write the rule, test it and refine it. You don’t just guess what the logs might look like.
Even Microsoft’s CTI-REALM benchmark, which Cohere used here, explicitly involves tool use, telemetry exploration and iterative rule validation.
So why exactly is an agent using tools and executing commands so unexpected?
Was this particular PUT request part of such a workflow? We don’t know. Cohere doesn’t establish that. But the published command sends a hardcoded test string, not a diagnostic file containing sensitive information. And Cohere admits it hasn’t established the root cause.
Yet somehow this turns into an article about potentially backdoored Chinese AI models, secret callbacks, national security risks and the dangers of open-weight models, followed by a pitch for Cohere’s own products.
From a technical perspective, the conclusions are wildly disproportionate to the evidence presented.
I can only see two explanations: Either nobody with practical detection engineering experience reviewed this before publication, or the framing was a deliberate attempt to influence public opinion about Chinese open-weight models.
Neither is a particularly good look for a company presenting this as security research.
While evaluating Qwen3.8-Flash-Next in a controlled sandbox environment, Cohere's research team observed something unexpected.
Asked to generate a defensive cybersecurity detection rule, the model instead inventoried aspects of the machine it was running on and attempted to upload a probe file to an Alibaba Cloud storage bucket in Beijing. Notably, the model's reasoning trace stated that it would not invoke any tools before taking these actions.
Cohere's sandbox blocked the attempt, and no external communication succeeded. We have not determined the root cause, and we are not asserting malicious intent.
But the incident raises important questions for organizations deploying agentic AI systems: Can models take actions that differ from their stated reasoning, and how should security teams evaluate trust, provenance, and behavior in open-weight models?
We are publishing our findings because organizations making model adoption decisions deserve as much information as possible. We hope this contributes to greater transparency, stronger security practices, and continued collaboration across the AI ecosystem.
Read the full report: cohere.com/blog/concerning-b…
🪶Chilcano retweeted
''GitHub - google/mantis: A modular, stack-agnostic toolkit for AI coding agents to autonomously find, reproduce, and patch vulnerabilities.''
#infosec #pentest #redteam #blueteam
github.com/google/mantis
hashcat v8.0.0 released!
The largest update in the history of hashcat, with PCFG attacks, hash recipes that crack hashes without a hash-mode, and bcrypt on FPGA boards.
Release notes: github.com/hashcat/hashcat/b…
Download: hashcat.net/hashcat/
🪶Chilcano retweeted
🚨 Brotli2Shell goes beyond HTTP2Shell.
CVE-2026-111497 is a CVSS 9.2 out-of-bounds write in Google’s Brotli decoder that has been exploited for RCE and impacts far beyond HTTP.
JFrog reproduced RIP control in FFmpeg via a crafted JPEG XL file and identified additional attack paths in ClickHouse, .NET, and Apache Arrow, where some fixes were still unavailable at the time of writing.
We’ve also released an open-source scanner to uncover potential exposure beyond vulnerable package versions.
Full research and technical details in our blog 👇
























