Repository navigation
Add prompt-injection-observation object template - #548
Merged
adulau merged 1 commit intoOct 16, 2026
Merged
Conversation
Member
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add prompt-injection-observation object template
What this adds
A new object template
prompt-injection-observationfor recording and sharing observed prompt injection / jailbreak attempts against AI systems.Attributes:
prompt-text— the malicious prompt as observed (required)technique— how it was done (instruction-override, roleplay, encoding-obfuscation, multi-turn-escalation, indirect-injection, delimiter-escape, tool-use-hijack, data-exfiltration-prompt, unknown)target-model— which model was targetedsuccessful— did the model follow the injected instructionsmodel-response— summary of what the model diddetection-method— how the attempt was noticeddeployment-context— what kind of AI app was hit (chatbot, code assistant, agent with tools...)mitigation— what was done about itfirst-seen/last-seen,reference,commentWhy
AI systems are being attacked the same way web apps are, but there is no standard MISP object to share these incidents in. The existing
ai-chat-promptobject covers normal, benign prompts — nothing covers the malicious ones. I work in detection and this is the piece I kept missing when trying to log and share these attempts.Gap check
I searched all 450 directories under
objects/for anything namedprompt-injection,jailbreak, orprompt: onlyai-chat-promptexists (benign prompts). Nothing models a malicious prompt injection attempt.Validation
The new
objects/prompt-injection-observation/definition.jsonpasses the repo's own checks:jsonschema -iagainstschema_objects.json— OKunique_uuid.py— OK (uuid2e7de182-3f86-4105-beb7-b6b0c03484a7is unique)tools/validate_opposites.sh— OKjq -S -j ., sorted keys, no trailing newline)Only one new directory is added; nothing else in the repo was touched.
Thanks for reviewing.