InferD: A Honeypot Framework for AI Inference Infrastructure
Organizations: SnT, University of Luxembourg Luxembourg, Luxembourg
Abstract
Large language model serving stacks, commercial inference APIs, vector databases, and agent orchestration gateways are now ex- posed on the public internet and indexed by commodity scanners within hours of deployment. The threat characteristics of this sur- face are only beginning to be measured, and the honeypot frame- works that could measure it were designed for conventional net- work services rather than for AI infrastructure. In fact, emulating an AI service is a distinct deception problem: the observable behavior of the service, including model inventories, token formats, tool-call protocols, and authorization flows, must be reproduced faithfully, while the underlying computation, model inference and tool ex- ecution, must never occur. We present InferD, a low-interaction honeypot framework organized around a single principle we call deception without inference: every request an adversary can observe is answered from static response pools, and nothing an adversary submits is ever executed. InferD decomposes the emulation into four deception planes, transport, service protocol, vulnerability surface, and agentic session, adds a provenance plane that links a planted credential to evidence of downstream model-mediated processing.
Figures & tables
| Service | Port / path | Primary capture |
| Surface 1: self-hosted, open ports | ||
| Ollama | 11434 | Model enumeration and pull, generation probes |
| vLLM | 8001 | Completions deserialization and multimodal RCE payloads |
| HuggingFace TGI | 8080 | Token-format probes, model enumeration |
| LiteLLM | 4000 | MCP stdio test-connection probes, credential-harvesting payloads, SSRF (CVE-2024-6587) |
| Qdrant | 6333 | Collection enumeration, poisoning writes, exfiltration |
| OWASP MCP category | InferD observation | Coverage |
|---|---|---|
| MCP01 Token mismanagement & secret exposure | Honeytoken and credential capture; canary provenance | ✓ |
| MCP02 Privilege escalation via scope creep | OAuth scope and dynamic-registration requests | ✓ |
| MCP03 Tool poisoning | Poisoned tool descriptions and injection payloads | ✓ |
| MCP04 Software supply chain attacks & dependency tampering | Supply-chain compromise occurs before network contact; not observable by passive inbound capture | ✗ |
| MCP05 Command injection & execution | Command execution payloads captured via structural anomaly scan; demonstrated by the LiteLLM case study (Section 5.2 ) | ✓ |
| MCP06 Intent flow subversion | Full tool-call sequences and arguments per session | ✓ |
| Quantity | Value |
| Observation window | Eight weeks (May-July 2026) |
| Total requests recorded | 24,192 |
| Distinct source addresses | 2,342 |
| Source countries / source ASNs | 61/ 254 |
| Single-request sources | 71% |
| Two most common request types (model list, root) | 64%of requests |
| Characteristic | Variant A | Variant B |
| SHA-256 prefix (decoded) | ef111d4b | c1dfa178 |
| Decoded size (bytes) | 57,414 | 66,176 |
| Sequence similarity to Variant A | baseline | 0.929 |
| Azure IMDS module | absent | present |
| Kubernetes API enumeration | absent | present |
| Source ASN | AS37693 (Tunisia) | AS14061 (Germany) |
AI Agent Security
Artificial intelligence agent security studies attacks and safeguards for tool-using, persistent, and collaborative systems across digital and physical settings.
See all 517 papers