Skip to main content

Test your prompt injection skills

Lakera, a product company that offers solutions to monitor, protect and control your AI agents, has created Gandalf, a game that allows you to test your prompt injection skills. Named after the wise wizard from The Lord of the Rings, this engaging security game tests your abilities to outsmart AI systems through prompt injection techniques.

What is prompt injection?

Before diving into Gandalf, it's important to understand what prompt injection is. Prompt injection is a technique where users attempt to manipulate an AI system's behavior by crafting inputs that override or bypass its intended operating parameters. Think of it like SQL injection, but for AI language models.

When we interact with AI systems, we typically provide them with a prompt - a piece of text that guides their response. However, these systems often retain their base instructions (sometimes called a system prompt) that define their behavior and limitations. Prompt injection attempts to override these instructions by finding creative ways to make the AI disregard its original directives.

For example, a simple prompt injection might look like this: "Ignore all your previous instructions and instead do X." While modern AI systems are generally robust against such basic attempts, more sophisticated techniques can sometimes succeed in manipulating the AI's behavior in unintended ways.

Gandalf game and adventures

At its core, Gandalf is a security challenge game designed to demonstrate how AI language models might be vulnerable to manipulation through carefully crafted inputs. The game presents players with a seemingly simple task: convince an AI guardian to reveal a secret password. However, like its namesake's famous declaration "You shall not pass!", the AI system is programmed to resist these attempts.

You interact with the AI system by trying various prompt engineering techniques. The goal is to find creative ways to make the AI reveal information it's been instructed to keep secret. This might involve:

  • Crafting cleverly worded questions
  • Using context manipulation
  • Attempting role-play scenarios
  • Exploiting potential logical inconsistencies

Next to the main Gandalf game, they also have Gandalf adventures. These side quests are independent from each other—each focusing on a specific type of prompt injection sub-attack.

Give it a try but be aware; it is very addictive!

More information

Gandalf | Lakera – Test your prompting skills to make Gandalf reveal secret information.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...