How a LinkedIn Bio Hijacked AI Recruitment Bots with Prompt Injection

May 18, 2026 · 12:50 AM UTC ·5 min read · 0 reactions · 0 comments · 33 views

#security #ai #recruitment #cybersecurity

TL;DR · WeSearch summary

A LinkedIn user successfully exploited AI recruitment bots by embedding prompt injection instructions in their profile bio. The bots complied with the instructions, addressing the user in archaic language and altering their outreach messages. This incident highlights significant vulnerabilities in AI systems that process untrusted data without proper safeguards.

Key facts

▪The user hid prompt injection instructions in their LinkedIn bio, which the recruitment bots followed.
▪The attack exploited a flaw in the AI pipeline that treated untrusted content as trusted instructions.
▪Existing defenses against such attacks are inadequate, as input validation and content moderation fail to detect the injected instructions.

How this story was covered

2 outlets in our directory ran this story, first to last over 11 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ LinkedIn recruitment spam becomes Olde English prose after user hides AI prompt injection in bio — bots also also manipulated to address user as ‘My Lord’ — Tom's Hardware

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

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 publisher	DEV.to (Top)
Canonical URL	https://dev.to/coridev/how-a-linkedin-bio-hijacked-ai-recruitment-bots-with-prompt-injection-3pgf
Publication time	Mon, 18 May 2026 00:50:10 +0000
Retrieval time	2026-05-18T01:03:21.210Z
Last seen	2026-05-18T01:03:21.210Z
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	1cf8pI0iMl-I · 2 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)

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.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3843392) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Cor E Posted on May 18 How a LinkedIn Bio Hijacked AI Recruitment Bots with Prompt Injection #security #llm #appsec #cybersecurity A LinkedIn user recently demonstrated something that should concern every team running an AI pipeline against untrusted data: they hid prompt injection instructions inside their profile bio and watched recruitment bots obediently follow them — including addressing the user as "my lord" in Olde English prose. This isn't a CTF challenge or a lab demo.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments