ghost-huntAI safety check
New stack.
New review.New tech.
New questions.
LLMs, agents, RAG pipelines. Six classes of risk that weren't in your last pentest - worked through one at a time, in shadow-mode, against your stack.If you're using AI tools, chatbots, or a knowledge base anywhere on your site, they carry new kinds of weak spots that older security checks don't look for. Here are six of them, explained plainly.
01
Prompt injectionHidden commands hijacking your AI
Attacker-crafted text hidden in documents, emails, or tool outputs hijacks your AI into running their instructions.Malicious text hidden inside documents, emails, or tool results that tricks your AI into following someone else's orders.
checked: injection resistance of exposed AI surfaceswe check: whether hidden instructions can steer your AI
02
RAG poisoningTainted knowledge base
Seeding your knowledge base with adversarial content that changes what your assistant answers. Invisible in logs.Someone plants fake or misleading content in the knowledge your AI reads from - quietly changing the answers it gives, with no trace in the logs.
checked: source integrity of the retrieval corpuswe check: whether your AI's sources can be quietly swapped
03
Supply-chain compromiseContaminated software parts
Malicious packages, poisoned weights, typosquatted deps. One bad import and you ship an attacker's backdoor.Bad code or bad model weights slip in through the software you install. One contaminated piece and you ship a back door without knowing.
checked: dependency provenance and signatureswe check: where your software parts really come from
04
Model extractionCloning your AI
Systematic querying that reconstructs your fine-tuned model's behaviour for the cost of an API budget.Someone uses your AI enough to rebuild a copy of it themselves - stealing the work you put into training it for the price of API calls.
checked: rate limits and query-pattern exposurewe check: how easily your AI could be farmed and copied
05
Tool-use abuseAI running commands it shouldn't
Your AI agent has filesystem, shell, and network access. One crafted instruction and it runs attacker commands.Your AI can read files, run commands, and make network calls. A single crafted prompt can turn that access against you.
checked: tool scopes and agent blast radiuswe check: what your AI is allowed to touch if tricked
06
Perimeter erosionForgotten public endpoints
Dev envs exposed publicly. Webhooks from third parties. OAuth scopes past memory. Classic holes, modern scale.Test environments that accidentally ended up public. Old webhooks you forgot about. Permissions no one remembers granting. Classic mistakes at modern scale.
checked: forgotten endpoints, webhooks, OAuth scopeswe check: doors you forgot are open