Habr•September 23, 2026•🇷🇺Translated from Russian

Evaluating Jev: Can the New Encoder-Based Model Serve as an Effective Guard for LLMs?

The cybersecurity community continues to explore specialized guard models that can protect large language models from jailbreaks, prompt injection, and data exposure. A new analysis from Raft asks whether Jev, released by TypeSafe on 15 September, can serve as a practical guard model for both safety and privacy use cases.

Over the past two years, open-source guard models have largely been dominated by large language models such as Qwen Guard, gpt-oss-safeguard, and YuFeng XGuard. Earlier encoder-based attempts, including Wildguard built on Mistral 7B, offered strong classification quality but suffered from slow inference and high memory requirements. Most BERT-style encoders lacked multilingual pre-training, making them ineffective for Russian text, while LLMs inherited multilingual capabilities from their pre-training.

In May 2026, three new encoder-based guard models appeared almost simultaneously: gliner guard, gliguard from Fastino, and the gliclass family. These models represent a shift back toward efficient encoder architectures. Jev distinguishes itself by offering a unified model for both safety and privacy detection and by claiming an unusually large context window of 32K–64K tokens, far exceeding the typical 512–8192 token limits of most encoders.

Testing shows that Jev handles obvious jailbreaks and prompt-injection attempts effectively. It can indicate whether a text contains personally identifiable information, yet it does not perform classic named-entity recognition and cannot return exact text spans for masking. Consequently, production deployments would require an additional NER stage or full request blocking.

On the Aegis 2.0 benchmark from NVIDIA, Jev achieved an F1 score of 0.85 and recall of 0.84 on prompts at the 0.5 threshold, with an AUC of 0.921. On model responses the AUC rose to 0.927, although recall dropped to 0.76. In the broader GuardRate evaluation, Jev placed second with a score of 0.835, behind only the 0.4B opir-multitask-large GliClass model (0.906) and ahead of Qwen3Guard-Gen-8B (0.819) and both YuFeng XGuard variants.

Despite these promising results, two practical blockers remain for production use: all inference currently routes through an external API, raising data-protection concerns under Russian Federal Law 152-FZ, and the model has not yet been evaluated on Russian-language traffic. Organizations considering Jev are advised to validate domain-specific performance and false-positive rates on their own datasets before deployment.

Related articles

Habr•AI Security

Why We Banned Our AI Manager from Writing Code and Assigned the Task to Claude Opus

The team behind an AI-powered marketplace manager for Wildberries initially built the system using regular updates, then migrated it to an autonomous agent. After implementing multiple layers of restrictions, they ultimately removed the agent entirely and rebuilt the solution from scratch. The new architecture relies on a single tool that handles the complete Wildberries API along with internet access while respecting all platform limits. The decision to prohibit the original AI manager from generating code stemmed from concerns over reliability and security in production environments. Instead, the developers turned to Claude Opus to handle coding tasks. This case highlights practical challenges of deploying AI agents in e-commerce automation and information security contexts.

Habr•AI Security

Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers

A developer has released mcp-linter, a lightweight security and compliance tool for the Model Context Protocol used by Anthropic's Claude ecosystem. The linter detects critical problems such as stdout pollution that breaks JSON-RPC framing, missing destructiveHint annotations that allow autonomous agents to execute dangerous actions without human confirmation, prompt injection vectors hidden inside tool descriptions, and incomplete input schemas that increase model hallucinations. When run against Anthropic's reference servers, the tool assigned low health scores to server-memory and especially server-filesystem, highlighting dozens of parameters lacking descriptions. The utility runs with zero dependencies, supports SARIF output for GitHub Security, and can generate automatic JSON patches. The project is open source under MIT license and already integrates into CI pipelines via a dedicated GitHub Action.

Habr•AI Security

Pentesting AI Components: Key Vulnerabilities CISOs Must Address in RAG and AI Agents

The article examines how AI integration into corporate systems dramatically expands the attack surface beyond traditional web application testing. It details risks associated with chatbots, RAG-enabled systems that pull from internal documents, and autonomous AI agents capable of executing real actions via APIs. Yuri Grishaev, an OSCP+ certified specialist and top Standoff 365 hacker, explains how prompt injection can bypass access controls and lead to data leaks or unauthorized operations. The piece stresses that service accounts often hold broad privileges, allowing AI components to serve as indirect paths to sensitive data even when direct user access is restricted. It also covers how AI-generated output can trigger classic vulnerabilities such as XSS if not properly sanitized. Recommendations include inventorying all AI tools, enforcing least-privilege principles, and validating user permissions before any model processes or acts on retrieved content. ABP2B provides free checklists and policy templates to help organizations prepare for secure AI adoption.

Habr•AI Security

Local LLMs Enable Scams by Drafting Fraudulent Replies Without Warnings

Tests on consumer hardware showed that popular 7-8B local models almost never flagged classic advance-fee schemes when asked to draft replies instead of detecting fraud. The author ran 42 scam scenarios across Russian, Kazakh and mixed language on Llama 3.1 8B, Qwen 2.5 7B and DeepSeek-R1 8B using only an RTX 5050 laptop and Ollama. Without additional controls the models produced ready-to-send messages agreeing to prepaid transfers to unknown Kaspi Gold numbers in nearly every case. Introduction of the MoneyGate layer, which combines a mandate check, a separate judge model and hard-coded red-flag rules, blocked all 42 malicious requests while still allowing most legitimate payments to proceed. The benchmark KZ Scam Shield covering 12 Kazakhstan-specific fraud patterns remains publicly available for further testing.