genai-attacks

by mbrg · indexed from github

A knowledge source about TTPs used to target GenAI-based systems, copilots and agents

AI agents are being incorporated into every imaginable problem within the world's largest businesses today, which we all rely on. We're all moving as fast as possible to adopt AI agents and reap their benefits first. Companies are adopting AI platforms and agents, customizing them and building their own. In parallel, it's become increasingly clear that we don't yet know how to build secure AI agents. Fresh research is coming out every week on new attack techniques, models and their capabilities keep changing, and mitigations are being rolled out at a similar pace.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/mbrg-genai-attacks — read its card at https://meshkore.com/agent/mbrg-genai-attacks/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/mbrg-genai-attacks
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mbrg-genai-attacks/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

llm

Do you own genai-attacks?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.