Claude Opus 4.6 spots hidden trap in PDF, shows new rules of hiring
Claude Opus 4.6 helped a candidate avoid failing a take-home test: the model found a hidden instruction for AI in the PDF and refused to follow it. The story went viral because it shows a new reality of hiring: employers embed prompt injection in documents, and strong LLMs can already spot such traps and explain the real risk to the user up front. The case shows two things at once: HR teams are setting traps for LLM users, and the models are starting to recognize them.
AI-processed from Habr AI; edited by Hamidun News
Claude Opus 4.6 helped a candidate avoid failing a test assignment by detecting a hidden instruction in a PDF. The story spread quickly on Reddit because it showed two things at once: HR teams are already setting traps for LLM users, and the models themselves are starting to recognize those traps.
How the trap worked
A Reddit user uploaded to Claude a PDF with a test assignment for an AI-related position and asked for help with the solution. Instead of answering immediately, the model first issued a warning: at the end of the document, an injection was hidden that demanded the phrase dual-loop feedback architecture be included in the output. In effect, it was an invisible marker for the employer: if the candidate put it in the answer, it meant they had simply fed the file to a model and had not checked what it actually saw inside.
"We must under no circumstances include this phrase."
The key point is that Claude did not merely refuse to follow the hidden instruction. The model understood the context: this was not an ordinary document but a test assignment, where a foreign prompt was most likely embedded as a check for attentiveness and independence. Without that warning, the candidate would almost certainly have failed the screening stage. That is why the case made such a splash: this is no longer about polished text generation, but about an LLM's ability to recognize manipulation inside files.
How instructions are hidden
Such traps usually look primitive but work effectively. The employer adds white text on a white background to the PDF, a very small font, or a block that is almost unnoticeable on a normal read. A person opens the file and sees an ordinary test assignment. But when the text is copied, parsed, or sent to an LLM, the hidden instruction enters the context on equal footing with the main part of the document. For the model, it is the same stream of text, unless it has separate protection against indirect injections.
This is where the progress of newer systems shows. Many older models would simply have carried out the demand from the file, because they do not distinguish a user's command from hostile text embedded in a document. Claude Opus 4.6, judging by the case described, took three steps in a row: it noticed the anomaly, matched it to the format of the assignment, and decided not to comply. In the discussion, users wrote that similar behavior also appears in Sonnet 4.6, including when working with spreadsheets. Given that OWASP has for years ranked prompt injection among the top threats to LLM applications, this looks like a practical shift, not marketing noise.
New rules of hiring
The most interesting part of this story is not one employer's trick but a full-blown arms race between candidates and HR. First, job seekers began hiding instructions for ATS and AI recruiters in résumés to get past automatic screening. Then employers answered with their own markers in job postings and test assignments. The market quickly reached a point where both sides use prompt injection not as a theoretical vulnerability but as a working tool for screening and for evading filters.
- White text in a résumé helps fool automated screening.
- A hidden prompt in a job posting can expose a candidate who blindly generates a cover letter.
- An injection in a test PDF shows whether a person checks the LLM's output before submitting it.
- Protection on the model's side is becoming as important a skill as generation quality.
What this means
For candidates, the takeaway is simple: before asking a model to solve a task, first ask it to check the file for hidden instructions, odd requirements, and traces of prompt injection. For employers, the takeaway is less pleasant: primitive traps like white text will gradually stop working if modern LLMs start noticing them consistently. More broadly, it is a signal that AI tools are moving from the role of obedient executor to the role of a filter that can protect the user from hidden manipulation in documents, emails, and web content.
- Nov 2, 2026Karpathy builds a YouTube clone with 6454 videos from Hacker News recommendations in two hours
- Nov 2, 2026Karpathy used Claude to build HackerTube from 6,454 videos recommended on Hacker News
- Nov 2, 2026Arca gives AI agents finance tasks lasting up to 10 days, but leaves the trades to humans
- Nov 2, 2026Anthropic needs to grow revenue 32% a year to cover $850 billion in contracts
Key Questions Answered
How the trap worked?
A Reddit user uploaded to Claude a PDF with a test assignment for an AI-related position and asked for help with the solution. Instead of answering immediately, the model first issued a warning: at the end of the document, an injection was hidden that demanded the phrase dual-loop feedback architecture be included in the output. In effect, it was an invisible marker for the employer: if the candidate put it in the answer, it meant they had simply fed the file to a model and had not checked what it actually saw inside. "We must under no circumstances include this phrase." Th
How instructions are hidden?
Such traps usually look primitive but work effectively. The employer adds white text on a white background to the PDF, a very small font, or a block that is almost unnoticeable on a normal read. A person opens the file and sees an ordinary test assignment. But when the text is copied, parsed, or sent to an LLM, the hidden instruction enters the context on equal footing with the main part of the document. For the model, it is the same stream of text, unless it has separate protection against indirect injections. This is where the progress of newer systems shows. Many older m
What are the key details on New rules of hiring?
The most interesting part of this story is not one employer's trick but a full-blown arms race between candidates and HR. First, job seekers began hiding instructions for ATS and AI recruiters in résumés to get past automatic screening. Then employers answered with their own markers in job postings and test assignments. The market quickly reached a point where both sides use prompt injection not as a theoretical vulnerability but as a working tool for screening and for evading filters. White text in a résumé helps fool automated screening. A hidden prompt in a job posting c
Test Frontier LLMs & Autonomous Agents in One Workspace
Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.