Suspicion is cheap
Generic tools can flag odd code paths, dangerous APIs, or broad classes of risk without proving the issue matters in the product.
ZeroQuarry research is where validated findings become public lessons. We publish after responsible disclosure, with enough technical detail to be useful and enough restraint to protect users still updating.
Generic tools can flag odd code paths, dangerous APIs, or broad classes of risk without proving the issue matters in the product.
Research starts with agent discovery, then pushes toward reachable impact, disclosure evidence, patch context, and safe public explanation.
Every validated pattern informs future testing: prompts, scanners, report language, confidence scoring, and evidence packet structure.
Not all AI models are equally good at security research. Some are great at spotting suspicious code, others are better at validating real vulnerabilities, and the best results often come from combining them in a multi-agent workflow.
In the battle of the 'frontier models' and 'bad actors', most software shops are getting caught in the middle. Multi-agent orchestration is the only viable solution to modern product security
ZeroQuarry identified a number of serious vulnerabilities in the Excalidraw plugin. We engaged in a coordinated disclosure with Obsidian and the plugin maintainer. This writeup explains the impact, disclosure process, mitigation tradeoff, and lessons for plugin ecosystems.
ZeroQuarry identified a critical RCE path in the Obsidian Tasks plugin and coordinated disclosure with Obsidian and the plugin maintainer. This writeup explains the impact, disclosure process, mitigation tradeoff, and lessons for plugin ecosystems.
Agents explore source, binaries, reachable services, trust boundaries, and product-specific behavior.
Findings are challenged for reachability, impact, affected versions, and evidence quality before disclosure.
Maintainers get scoped reports, patch context, and time to investigate or ship mitigations.
Writeups become public only when the disclosure posture is appropriate and the detail level is safe.
Community plugins, app extensions, and integration points often inherit powerful permissions with inconsistent review.
Rich content formats can cross from document parsing into script execution, file access, and trusted UI behavior.
Local file systems, embedded browsers, sync features, and convenience APIs create unusual trust boundaries.
The interesting bugs often live in business logic, authorization edges, request routing, and stored credentials.
AI features connect prompts, tools, files, secrets, and users in ways traditional scanners rarely model well.
Open-source packages, generated artifacts, and release automation become attack surface as soon as products depend on them.