WeWorkBuddy

Show HN: Intrusive.ai – open-source AI attack simulation

I created the INTRUSIVE.AI platform to give agent builders the ability to evaluate their agents against OWASP's Top 10 for Agentic Applications (and more generally, just to allow for comprehensive testing in a non-production environment). Through my own experience with evaluating agents, I found indirect prompt injection testing to be especially difficult due to the architectural nature of it. To overcome that challenge, I created Interceptor Sandbox - a sandbox that runs agents in a simulated e

Read original source
Source reference for Show HN: Intrusive.ai – open-source AI attack simulation. Screenshot not yet available.
Source record · preview pending · news.ycombinator.comOpen the source for the full page.

Source record

Recorded metrics

points · 3 votes
2026-11-19 01:24:13.081Z
cumulative since publication

Research analysis

Project record

Source account: I created the INTRUSIVE.AI platform to give agent builders the ability to evaluate their agents against OWASP's Top 10 for Agentic Applications (and more generally, just to allow for comprehensive testing in a non-production environment). Through my own experience with evaluating agents, I found indirect prompt injection testing to be especially difficult due to the architectural nature of it. To overcome that challenge, I created Interceptor Sandbox - a sandbox that runs agents in a simulated e

Observed adoption & comparisons

Source votes: 3 votes (Nov 19, 2026 UTC; cumulative since publication) Recent records to compare: “affaan-m/ECC” (Trendshift, Nov 19, 2026); “mvanhorn/last30days-skill” (Trendshift, Nov 19, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.