Other models wouldn't verify the hole. Grok proved it and proposed a fix
Their own code, their own database, on their own laptop. OpenAI's models and Claude found the issues but refused to confirm them. Grok tested that they were exploitable and suggested a fix.
Done withGrokSpotted· by HN user vorticalbox· Oct 18, 2026
Result Tested on their own copy, fix proposed
“grok however found the same issues, tested to make sure it was exploitable and proposed a fix.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
With the full source code and a database running on their own laptop, they asked AI models to check for security issues. OpenAI’s models and Claude found issues but refused to verify that they existed.
How it went
Grok found the same issues, tested to make sure they were exploitable, and proposed a fix.
Try it yourself with Grok
This is my own application: [source code], with a local test database at [connection]. Review it for security vulnerabilities. For each one, write a safe proof-of-concept test that runs only against my local copy, confirm whether it's exploitable, and propose a fix with the code change.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
lldb behaved differently through Python in Docker than on their own Linux box. Grok 4 traced it to how address sanitizer works in each environment. They're impressed so far.
The script came out almost perfect on the first try, except for a one-character typo in the file-path code. Finding it took an hour: the hidden cost of code that's nearly right.
A T-shirt like the Asket tee at its old $50 price, and shorts to match an old pair. Grok invented a few review claims on the way, but both picks turned out right.
The repair cost too much, so they gave Grok a must-have list: low mileage, big trunk, 40+ MPG, under budget, near the dealer. It found a 2020 Ford Escape Hybrid.
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.