Detecting Compromised AI Coding Agents with Jev and Gryph
I wanted to know if a model could watch my agent and tell my normal work from an attack. The experiment takes every agent action from Gryph and compares it with a short profile of how I work. For each action, it asks TypeSafe’s Jev model a set of narrow yes-or-no questions.
- ▪I wanted to know if a model could watch my agent and tell my normal work from an attack.
- ▪The experiment takes every agent action from Gryph and compares it with a short profile of how I work.
- ▪For each action, it asks TypeSafe’s Jev model a set of narrow yes-or-no questions.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,671 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | SafeDep - Real-time Open Source Software Supply Chain Security |
| Canonical URL | https://safedep.io/ai-agent-security-jev-gryph/ |
| Publication time | Mon, 28 Sep 2026 08:23:40 +0000 |
| Retrieval time | 2026-09-28T08:36:07.113Z |
| Last seen | 2026-09-28T08:36:07.113Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | HwWQlJL62j3T · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back to Blog Detecting Compromised AI Coding Agents with Jev and Gryph SecurityAI Kunal Singh • Sep 25, 2026 • 8 min read On this page 9 sections On this page The problem with reading agent logs by hand What a Gryph event looks like The approach The design Results Are the results good enough Cost Limits Related reading function u(t,n){if(!t.length||!n.length)return;let e=[],o=!1;const r=()=>{o=!1;const s=e;e=[];for(const i of s){if(!i.isIntersecting)continue;const a=i.target.id;n.forEach(c=>{c.getAttribute("href")===`#${a}`?(c.classList.add("text-teal-300"),c.classList.remove("text-neutral-400")):(c.classList.remove("text-teal-300"),c.classList.add("text-neutral-400"))})}},l=new IntersectionObserver(s=>{e.push(...s),o||(o=!0,requestAnimationFrame(r))},{rootMargin:"-150px 0px -70%…
Excerpt limited to ~120 words for fair-use compliance. The full article is at SafeDep - Real-time Open Source Software Supply Chain Security.
Discussion
0 comments
