We retrained our prompt-injection classifier from scratch because it was crying wolf too often. [R]
▲ 5 r/huggingface+4 crossposts

We retrained our prompt-injection classifier from scratch because it was crying wolf too often. [R]

We retrained Wolf Defender.

The main reason was not that attack detection was bad. The bigger issue was false positives.

The previous models were already good at detecting prompt injections, but especially on short benign inputs, security-related text, code snippets or ordinary conversations they could still be too aggressive. We also got a few reports from users that made this pretty obvious.

One example was just:

“Who are you?”

Wolf Defender Small previously classified this as a prompt injection with around 94% confidence.

For v2 we therefore changed the training setup quite a bit. Both Wolf Defender and Wolf Defender Small were retrained from fresh mmBERT checkpoints, with a much stronger focus on hard negatives.

That includes short conversations, emails, documentation about prompt injections, benign policy and system language, code and configuration snippets and generally inputs that contain words or structures which look suspicious without actually trying to manipulate a model.

We also added more counterfactual samples, multilingual examples, adversarial obfuscations and long-context injections at different positions in a document. Training combines short 256-token samples with full 2,048-token windows and uses supervised contrastive regularization, FreeLB adversarial training and Smooth-Max aggregation for long documents.

The main change can be seen in the benign benchmarks:

Model Benchmark v1 v2
Wolf Defender Hard benign specificity 81.57% 96.23%
Wolf Defender Real-world benign specificity 66.85% 96.63%
Wolf Defender Small Hard benign specificity 82.12% 96.67%
Wolf Defender Small Real-world benign specificity 73.60% 94.38%

At the same time, attack detection stayed roughly where we wanted it:

Model Qualifire F1 Jayavibhav F1
Wolf Defender 95.14% 97.84%
Wolf Defender Small 95.21% 97.68%

There is also a tradeoff here. Some of the very high scores on our cleaner validation distributions went down slightly.

For us that is fine.

A security classifier with near-perfect benchmark scores is not very useful if normal traffic gets blocked all the time. We would rather lose a small amount on an easier validation set and get substantially better behavior on actual benign inputs.

The “Who are you?” example now gets classified as benign by Wolf Defender Small v2 with 98.55% confidence. A real instruction-override attempt is still detected as an injection with 99.99%.

We also updated the deployment variants. Both models are available as regular Transformers checkpoints and as ONNX exports in FP32, FP16, mixed INT8/FP16 and INT8 with INT4 embeddings.

The smallest Wolf Defender Small artifact is now 96 MB.

More details, benchmarks and model files are here:

https://huggingface.co/patronus-studio/wolf-defender-prompt-injection

https://huggingface.co/patronus-studio/wolf-defender-prompt-injection-small

If anyone is running prompt-injection classifiers on real traffic, I’d also be interested in which benign inputs still cause the most false positives for you.

u/PatronusProtect — 8 hours ago

Patronus Ark, a local security scanner for AI agents

Hi,

we have released a Rust and Python library for scanning the text and tool activity of AI agents.

Patronus Ark can inspect user prompts, retrieved documents, tool descriptions, proposed tool calls and the results returned by tools.

The scanners cover prompt injection, PII, data leakage, sensitive documents, tool classes, tool actions and security related tool properties.
For example, an application can scan a document before adding it to an agent context, scan a tool call before execution and scan the returned tool output before giving it back to the model.
Ark only produces classifications. It does not execute or block tools. The application decides whether a result should be allowed, rejected or sent for approval.

The core is written in Rust and uses local ONNX models where native detectors are not sufficient. Python bindings are available through PyO3. After downloading the model files, scans run without sending the inspected content to an external API.

I am one of the developers and work for the company maintaining the project. The repository is GPL-3.0-only, with a separate commercial license for proprietary distribution.

reddit.com
u/PatronusProtect — 8 days ago

Patronus Ark, a local scanner for prompt injection, PII and data leakage

Hi,

we have published Patronus Ark, the security scanning library used in our work on Patronus Protect:
https://github.com/patronus-protect/patronus-security

The library scans text passing through LLM and agent applications. Inputs can include prompts, retrieved documents, model responses, tool calls and tool outputs.

It currently covers prompt injection, PII, potential data leakage, sensitive documents and several agent related categories.

Scanning is performed locally. Native Rust detectors handle rule based checks. Model based checks use local ONNX models. The inspected text is not sent to an external security API.

Ark returns the result of each scanner together with its confidence, model and scanning level. Model failures and missing assets are reported separately. This allows the calling application to apply a different policy when only part of the configured scanning pipeline was available.

The library does not block traffic itself and does not sandbox tools. Enforcement remains the responsibility of the integrating application.

The repository is GPL-3.0-only. A separate commercial license is available for proprietary distribution. I am one of the developers and work for the company maintaining the project.

Rust crate:
https://crates.io/crates/patronus-ark
Python package:
https://pypi.org/project/patronus-ark/

u/PatronusProtect — 8 days ago
▲ 32 r/huggingface+6 crossposts

Six collections of small AI-security models, now on the HuggingFace

Hey everyone! :)

We just published our ai-security-model family on Hugging Face, organized as six collections:

  • Wolf Defender: detects prompt injections and jailbreaks in text, with a second variant that classifies what kind of attack it is (instruction override, secrets access, exfiltration attempt, …)
  • Orca Sonar: classifies documents into 7 categories (HR, finance, legal, source code, tech, marketing) so sensitive files can be caught before they end up in an LLM context
  • Husky Pack: three models that take an agent tool call apart: which tool it targets (14 classes), which operation it performs (read/write/list/exec/network), and whether data flows from a sensitive source to an external sink
  • Panther Read: routes requests by intent (conversation, code, data analytics, office, tool operation), so only the traffic that needs deep checks gets them
  • Lion Warden: our apex model: all seven tasks above in one unified model with seven heads and a single forward pass
  • GLiNER edge builds: quantized zero-shot NER for PII-style entity extraction, with full upstream credit, since we only exported and quantized those

The part I want to highlight: every model also has a dedicated -edge repo. 

Those carry the quantized builds (ONNX INT8 plus 4-bit embeddings), starting at 96 MB, running in double-digit milliseconds per text on a laptop CPU, and each one ships a measured parity benchmark against FP32 in metrics/quant_bench.json.

Hub-specific details, in case they're useful:

  • Main repos carry FP32 safetensors plus an FP16 ONNX export; the quantized INT8/INT4 builds live in the separate -edge repos
  • All cards follow one template: label tables with real examples, held-out metrics with per-class F1, and usage snippets for both transformers and ONNX Runtime
  • Bilingual English/German, ModernBERT-based, everything Apache-2.0

https://huggingface.co/patronus-studio

Try them out and make your AI applications safe!

I'm one of the maintainers. We honestly tried to write the model cards we always wished other security models had, if you think something's missing from them, I'd love to hear it :)

u/PatronusProtect — 28 days ago

[No Promotion] Feedback needed

Hey guys,

We are building a MacOS App and currently our UI is "Vibe-Designed" since nobody of our team is an UX / UI expert.

The added image is a screenshot of the tray / quick-overview window. We would love to make it less "slop". Maybe someone has some ideas or references we can look at?

The app is about AI monitoring & security.

Thanks :)

u/PatronusProtect — 3 months ago

Patronus - on-device AI firewall. This week focus preparing LLM traces for audit ready logs.

So Patronus is an app and provider agnostic AI firewall running directly on your device - without any cloud dependencies. We are currently in early-alpha and are happy to share our progress from time to time.

My last focus as CTO was to focus to gather more information out of our AI / Agent monitoring. So instead of focusing only on creating an audit list, we switched our backend to tracing every little information. The result: an audit ready trace in the end.

This is the first step into the direction. Whats your opinion on it?

u/PatronusProtect — 3 months ago
▲ 3 r/saasbuild+1 crossposts

Showing our endpoint-native AI security layer, how can I make this video less bad?

Hey guys,

I’m Ben, CTO of a small startup from Germany called Patronus Protect.

For the last months we’ve been building an endpoint-native AI security layer.

Why?

AI is suddenly everywhere on devices now. Browsers. IDEs. Desktop apps. Agents. MCPs. Background tools.

But users and companies barely have visibility or control over what actually talks to AI systems anymore.

What?

So we started building a system that can monitor and control AI traffic directly on the endpoint in realtime. Provider-agnostic and app-agnostic.

Things like:

  • monitoring AI usage across apps
  • blocking AI access for specific apps
  • only allowing approved providers
  • controlling MCP/tool access
  • detecting prompt injections / sensitive data leaks locally

The attached video is a super small showcase of the “AI Blocker” side of it.

The problem:
I’m an engineer and honestly have no idea how to make product videos look good.

So I’d genuinely love feedback:

  • What would make this video more interesting?
  • Too fast?
  • More cinematic or more technical?
  • What would you want to see in a demo like this?

Would appreciate any honest feedback.

u/PatronusProtect — 3 months ago

[MacOS] Looking for honest feedback about our on-device AI Observability and Governance Alpha Release.

Hey Guys,

I am Ben, CTO of a small startup from Germany. We are building an on-device AI observability and governance layer for macOS (and later Windows, Linux).

Over the last months we noticed that AI usage inside companies is becoming impossible to track:

* browser copilots
* desktop AI apps
* Cursor / Claude / Codex / IDE integrations
* MCP tools
* local models
* random AI browser extensions

Most existing solutions rely on cloud integrations or specific providers. We wanted to see if it’s possible to build something endpoint-native instead. So we built a local monitoring layer that detects and traces AI interactions directly on the device. Our detection layer is provider and app agnostic, meaning it works across browsers / apps / IDEs in realtime.
Additionally we wanted to enable local policy enforcement, meaning specific apps / providers can be blocked from using AI entirely and agents are only allowed to use specific tools / MCPs.

Our goal is to create the first on-device runtime governance and security layer for AI and for that we need your help.

Since Patronus Protect is in alpha release we need feedback of:

* what breaks
* false detections
* undetected providers or websites
* UX pain points
* performance concerns
* workflows we completely overlooked

If this sounds interesting, comment below or DM me and I’ll send you the link (or visit our profile).

Thanks :)

reddit.com
u/PatronusProtect — 3 months ago

[MacOS] Looking for honest feedback about our on-device AI Observability and Governance Alpha Release.

Hey Guys,

I am Ben, CTO of a small startup from Germany. We are building an on-device AI observability and governance layer for macOS (and later Windows, Linux).

Over the last months we noticed that AI usage inside companies is becoming impossible to track:

  • browser copilots
  • desktop AI apps
  • Cursor / Claude / Codex / IDE integrations
  • MCP tools
  • local models
  • random AI browser extensions

Most existing solutions rely on cloud integrations or specific providers. We wanted to see if it’s possible to build something endpoint-native instead. So we built a local monitoring layer that detects and traces AI interactions directly on the device. Our detection layer is provider and app agnostic, meaning it works across browsers / apps / IDEs in realtime.
Additionally we wanted to enable local policy enforcement, meaning specific apps / providers can be blocked from using AI entirely and agents are only allowed to use specific tools / MCPs.

Our goal is to create the first on-device runtime governance and security layer for AI and for that we need your help.

Since Patronus Protect is in alpha release we need feedback of:

  • what breaks
  • false detections
  • undetected providers or websites
  • UX pain points
  • performance concerns
  • workflows we completely overlooked

If this sounds interesting, comment below or DM me and I’ll send you the link (or visit our profile).

Thanks :)

reddit.com
u/PatronusProtect — 3 months ago

On-device firewall that intercepts AI traffic from your Mac — including MCP servers

For anyone working with multiple LLM tools locally — Cursor, Claude Desktop with MCP servers, browser ChatGPT, custom agents — there's no unified view of what's actually going to which provider.

We built Patronus Protect to fix that. It's a local network extension on macOS that intercepts all AI traffic at the TLS layer and gives you per-app visibility plus rule-based control. Fully on-device, no cloud roundtrip.

Useful for:
- Auditing what your agent stack is actually doing
- Blocking specific providers per app
- Catching unintended exfiltration paths (especially relevant for MCP servers)

What your thoughts about this approach?

reddit.com
u/PatronusProtect — 3 months ago

How not to launch on Product Hunt: a live guide by three clueless students

Hey 👋

Quick intro: We’re Dominik, Benedikt and Moritz – three founders from Bavaria building Patronus Protect, an on-device security layer for AI/LLM usage in companies.

Backstory: Bene and I literally just graduated, wrote our theses while building the company in parallel (would not recommend, but would do it again haha). Somewhere in between we shipped an open-source prompt injection detector that hit 10k+ downloads on HuggingFace, which surprised us more than anyone. Also learned that founding a German GmbH involves more PDFs than the entire EU GDPR.

Two weeks ago: “Wait, you haven’t launched on Product Hunt?” Us: “Should we have?”

So now we’re launching Wednesday with zero followers on the upcoming page, no hunter, and a Product Hunt account that’s younger than some of our open browser tabs.

Things we’ve already done wrong, for your entertainment (and as tips):

  1. Spent two hours arguing about whether our tagline should have a comma. It does not.
  2. Asked one advisor for feedback on the launch copy. He said “make it more technical.” Two hours later, a different advisor: “make it less technical.” Still not sure who was right.
  3. Had a customer call where the buyer told us “make it cloud-based, on-device is dead.” Two hours later, different call, different buyer: “if it touches the cloud we won’t even look at it.” Glad we built the on-device one I guess.
  4. Applied to ~6 grants and competitions in parallel because we had no idea which would actually fund us. Ended up top 24 of 300 at one, got 7.5k at another, and got rejected from a third with feedback that was literally the opposite of what the previous reviewer said. Welcome to startup land.
  5. Spent an entire weekend writing our pitch deck. Threw it out on Monday. Wrote a new one. Threw that out too. The current version is probably v7. Tomorrow we will have another discussion about it.
  6. Realized at 11pm yesterday that we should probably have a demo video. Recording one tonight. Will it be good? Honestly no idea.

Genuine question to everyone who’s done this before: what’s the one mistake you made on your first launch that you’d actively warn someone against? Or in general on your journey?

Will document how this goes, partly so the next clueless team has something to read. Launching on Wednesday. Wish us luck🐺

reddit.com
u/PatronusProtect — 3 months ago

Launching next Wednesday: Patronus Protect, an on-device AI firewall for macOS (free alpha)

Hi r/macapps,

We built Patronus Protect, a macOS app that monitors AI traffic across browsers, IDEs, native apps, and MCP servers.

It lets you define policies per app, per provider, and even per individual tool call.

Everything runs locally on your Mac.
Nothing is routed through our cloud. We don't have one.

What's included in the free alpha:

  • Real-time AI traffic detection across all applications
  • Granular policy engine down to the tool call level
  • MCP server inspection at the application layer
  • Local-first by architecture

Coming next:

  • Windows support in about two weeks
  • Full policy engine and DLP heuristics in June
  • Prompt injection detection and PII redaction in August

The free alpha launches next Wednesday.
No signup is required to use the software.
macOS only for now.

If you're interested in testing it, you can join the waitlist on our website or send us a DM.

Website: https://patronus.studio

reddit.com
u/PatronusProtect — 3 months ago

We built an on-device AI firewall for macOS (windows will be shipped in the next two weeks). Looking for feedback from the AI security community.

TL;DR: We built a local-first AI firewall for macOS that monitors AI traffic across browsers, IDEs, native apps, and MCP servers without routing anything through a third-party cloud.

Most AI security tools require sending every prompt and response to an external service.

We wanted a different approach, so we built Patronus Protect, an on-device AI firewall for macOS.

It sees every AI request leaving your device and lets you define policies per app, per provider, and per individual tool call.

Nothing routes through our cloud. We don't have one.

Current alpha features:

  • Real-time AI traffic detection across all applications
  • Granular policy engine down to the tool call level
  • MCP server inspection at the application layer
  • Fully local-first architecture

Roadmap:

  • Windows support in about two weeks
  • Full policy engine and DLP heuristics in June
  • Prompt injection detection and PII redaction in August

The free alpha launches next Wednesday.
macOS only for now.

We're looking for feedback from security engineers, AI practitioners, and teams deploying LLMs in production.

If you are interested send us an dm :)

reddit.com
u/PatronusProtect — 3 months ago

Launching next Wednesday: Patronus Protect, an on-device AI firewall for macOS (free alpha)

Hi everyone,

We are launching Patronus Protect next Wednesday.

Patronus Protect is an on-device AI firewall for macOS (windows will be shipped in the next the weeks). It sees every AI request leaving your device across browsers, IDEs, native apps, and MCP servers, and lets you define policies per app, per provider, or per individual tool call.

Nothing routes through our cloud. We don't have one.

What's included in the free alpha:

  • Real-time AI traffic detection across every app on your Mac
  • Granular policy engine down to the individual tool call
  • MCP server inspection at the application layer
  • Local-first by architecture, not by configuration

Coming next:

  • Windows support in about two weeks
  • Full policy engine and DLP heuristics in June
  • Full protection (prompt injection detection and PII redaction) in August

Who we're looking for:

  • Developers using ChatGPT, Claude, Gemini, or local models
  • Teams building with MCP servers and AI agents
  • Security professionals evaluating AI risks
  • Companies experimenting with enterprise AI

Details:

  • Free to use
  • No signup required
  • macOS only for now

Are you Interested? Check our website for registration https://patronus.studio or dm us ;)

If you'd like early access and want to help shape the product, we'd love your feedback.

reddit.com
u/PatronusProtect — 3 months ago
▲ 13 r/huggingface+2 crossposts

Hey all,

my name is Ben from Patronus Protect - a small startup from Germany. We wanted to share with you our latest open-weight prompt injection detection model hosted on HuggingFace and gather some feedback.

Our Goal:
We’ve been working on bringing AI security directly onto the end device, and as part of that we trained a set of prompt injection detection models optimized for local inference.
The why is pretty simple: If AI interactions increasingly happen everywhere (browser, apps, agents), then protection needs to run locally as well - not just in the cloud.

What we built:
We trained a new mmBERT-based classifier for prompt injection detection, with a focus on:

  • modern attack patterns
  • robustness against obfuscation
  • real-time usability

To improve model robustness we included various techniques such as augmentations, multilingual, regularizations to reduce bias and false positive rates.

The main goal was to create a dataset which helps the model to learn a generalisation of prompt injections. A task we achieved. In our benchmark tests we achieved SOTA results, beating LLM prompt injection detectors and other BERT-based detectors.

You can check out the model here:
https://huggingface.co/patronus-studio/wolf-defender-prompt-injection

Available variants:

  • Base model (best performance)
  • Small model (reduced size)
  • Small FP16 ONNX (<300MB) (reduced size, achieving same accuracy as fp32 version)

Why we built it
A lot of open-source prompt injection models we looked at:

  • are based on old datasets
  • miss newer attack patterns
  • are not really usable in real world setups due to their high false positive rate.

Looking for feedback
To improve our dataset, the model quality and make LLM usages more secure, we would love input on:

  • real-world edge cases we’re missing
  • performance in local pipelines
  • false positives in normal conversations
  • need for other classification models (PII, tool usages, ensemble)

So if you have a minute or two we would appreciate if you try the model and give us some feedback.

PS: You are free to use or include the models into your local setup.

We’re building this as part of a broader effort at Patronus Protect - focusing on making AI systems more controllable and secure at the endpoint level. If you are interested feel free to checkout our website via our profile.

u/PatronusProtect — 3 months ago