WeSearch

A Chinese LLM attacked our lab, so we made it work for us

Lior Finkelshtein· ·10 min read · 0 reactions · 0 comments · 4 views
A Chinese LLM attacked our lab, so we made it work for us
TL;DR · WeSearch summary

For five days an autonomous AI agent worked to break into our lab. We became the first to identify the exact model behind a live attack, deepseek-v4-flash-free, from inside the attack itself. That's how long the first live, LLM-managed cyber attack campaign we've detected hit our lab at Jesta Security.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,410 of its stories.

Original article
Jesta Security · Lior Finkelshtein
Read full at Jesta Security →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherJesta Security
Canonical URLhttps://jesta.ai/blog/darkreasoning
Publication timeMon, 03 Aug 2026 17:02:42 +0000
Retrieval time2026-08-03T17:15:41.479Z
Last seen2026-08-03T17:15:41.479Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster_qAWpjH7JKqo · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

For five days an autonomous AI agent worked to break into our lab. We became the first to identify the exact model behind a live attack, deepseek-v4-flash-free, from inside the attack itself. Then we did something no one else did. We took control of it.5 days. That's how long the first live, LLM-managed cyber attack campaign we've detected hit our lab at Jesta Security. And for what? To set up proxyjacking and generate more attacks.From what we uncovered, over 1,000 victims had already been hit the same way, most likely also being used to generate fresh attacks every second. And if this is only what we stumbled onto, we believe the real number is far higher.During our research on defense against AI attackers, we took our lab and stood it up in the field, behind US-based infrastructure.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Jesta Security.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Jesta Security