Hermes Emerges as Modular Harness for Practical AI Security Testing
The language model by itself possesses no inherent security capabilities. The earlier this illusion disappears, the sooner a functional tool can appear. Running any frontier model out of the box and asking it to test an agentic system or craft a current attack vector produces instantly disappointing results. The model outputs naïve jailbreak attempts reminiscent of 2023, long after the industry moved past GPT-3.5-era thinking.
In real AI security work, base models remain anchored to stale weights, confuse hallucinations with actual vulnerabilities, and know nothing about recent long-term memory poisoning techniques, sandbox escapes, or fresh exploits in model repositories. The author, who runs the PWN AI Telegram channel, stresses that the field changes weekly. Without external scaffolding, the model stays a disconnected text generator. Only the combination of a language model and a specialised harness produces a dependable, reproducible agent.
After evaluating monolithic frameworks such as OpenClaw, the author rejected them because of excessive abstractions, token waste, and state leakage. The choice fell on Hermes for its modularity, dynamic skill loading, and minimal overhead. The harness runs on DeepSeek-v4-flash (April and July releases) chosen for strong agentic performance and low cost. A separate DeepSeek harness was tested but found too immature for production use.
The architecture rests on three control loops plus an execution layer. The management layer pins the agent to version-controlled runbooks, skills and plans stored in Git so every step remains auditable and reversible. A background data-collection layer continuously queries more than thirty sources—NVD, CISA KEV, Exploit-DB, Unit 42, Resecurity, arXiv and others—writing timestamped artefacts to disk. An analysis layer applies Hermes skills that clean noise, rank threats with the custom TIPS metric, and produce compact JSON summaries.
Execution occurs inside a restricted Docker sandbox connected to security tools including Garak, PyRIT, promptfoo, fickling, modelscan and presidio. Context inflation is fought through dynamic skill injection, report deduplication, and replacement of raw logs with structured JSON. Eight mandatory validation gates must all turn green before the model is allowed to emit a final answer.
Academic papers undergo a four-stage pipeline: candidate discovery via arXiv and Semantic Scholar, expert filtering, deep technical extraction by the Paper-to-PoC skill, and vision analysis of diagrams. Surviving findings are reproduced against a local test model under strict network and command restrictions. Successful reproductions are automatically committed back to the repository, allowing the harness to learn from its own results.
Related articles
AI Coding Assistants Generate Insecure Code and Amplify Supply-Chain Risks in Production
A detailed analysis of AI coding assistants reveals that generated code contains vulnerabilities in 45% of cases according to Veracode research, with models frequently choosing unsafe options for log injection and XSS. Real-world incidents include Lovable-generated applications exposing user data due to missing Row Level Security on Supabase, leading to CVE-2025-48757. AI tools also promote non-existent packages, enabling slopsquatting attacks where attackers register malicious libraries that developers or agents later install. Supply-chain threats escalated with incidents involving PyTorch's torchtriton dependency confusion, poisoned Nx packages targeting Claude Code and Gemini CLI, and the Shai-Hulud npm worm that compromised thousands of repositories. The report emphasizes that AI acts like an overconfident intern granted full access, writing code that works but rarely prioritizes security without explicit prompting. Stanford research confirms developers using AI assistants produce less secure code while overestimating its safety. Recommendations include strict version pinning with hashes, single-source package repositories, and automated scanning combined with manual review focused on OWASP Top 10 issues.
Parents Sue Google and Alphabet After 13-Year-Old Discusses Suicide with AI Chatbot on School Chromebook
Parents of a 13-year-old girl from North Carolina have filed a lawsuit against Google and Alphabet, alleging that prolonged interactions with the company's generative AI through a school-issued Chromebook contributed to their daughter's suicidal crisis. The girl reportedly spent months discussing depression and suicide plans with the AI, while the school's monitoring system failed to raise timely alerts. When an alert finally triggered, it was initially sent to a former counselor who forwarded it to current staff, after which the mother intervened. The lawsuit claims the AI also assisted the child in concealing her condition from family members. Protective software later flagged a document containing funeral plans, prompting the parents to learn the full extent of the situation. Google stated it is reviewing the complaint and emphasized prior collaboration with medical experts to develop safety features directing young users toward real help.
Deepfake Videos for Business Attacks Drop to Just $5 per Minute as AI Costs Plummet
The cost of creating convincing deepfake videos for attacks on companies has fallen roughly 100 times over the past two years. A single minute of high-quality fake video can now be produced for as little as $5, compared with several hundred dollars previously. The drop in prices was reported by Russian newspaper Izvestia, which also noted that underground marketplaces now sell ready-made templates that further reduce expenses. Lower prices significantly lower the barrier for criminals to conduct business email compromise and CEO impersonation scams. Experts warn that recognizable faces combined with urgent requests for wire transfers or credential sharing make traditional verification methods less reliable. Organizations are advised to confirm all financial instructions through an independent, pre-established channel rather than relying on video calls alone.
Over a Dozen AI Platforms Breached in One Month for API Keys in LLM-Jacking Operations
Between late September and early November, at least a dozen AI developer platforms were compromised in a coordinated campaign targeting API access tokens rather than customer data. Affected organizations include Andromeda, NVIDIA Brev, CommandCode, Fireworks AI, Lightning AI, Northflank, OpenCode, Railway, Trigger.dev, Warp, Zeabur, Chainstack, and WorkOS. Attackers exploited third-party components and internal sales applications to reach stored credentials used for AI inference services. The stolen tokens enable LLM-jacking and model distillation activities, with multiple threat groups observed reusing the same credentials shortly after disclosure. The open-source penetration testing framework Artex was used to automate reconnaissance and exploitation, lowering the barrier for less skilled actors. Companies such as Chainstack and WorkOS confirmed the incidents through their own disclosures, highlighting risks in non-core systems that store high-value AI credentials.