FraudGuard is an agent-driven honeypot system that actively engages scam conversations, detects malicious intent, extracts intelligence, and reports verified scam data through a controlled callback mechanism.
Designed for predictability, safety, and control, even when AI components are involved.
Scam communications today are adaptive, conversational, and resistant to static rules, often designed to extract sensitive information quickly.
FraudGuard flips the problem by:
- Engaging scammers instead of blocking them.
- Collecting intelligence without alerting the attacker.
- Terminating conversations safely.
- Reporting only verified results.
The system follows a strict, linear flow to ensure safety and control.
graph TD
A[Incoming Message] --> B[Decision Engine]
B --> C[Agentic Engagement]
C --> D[Intelligence Extraction]
D --> E[Safe Termination]
E --> F[Verified Callback]
style A fill:#f9f,stroke:#333,stroke-width:2px
style F fill:#9f9,stroke:#333,stroke-width:2px
Each step is controlled, state-aware, and non-aggressive.
| Feature | Description |
|---|---|
| 🧠 Intent Detection | Accurately identifies scam intent versus normal conversation. |
| 🤖 Agent Responses | Generates human-like, context-aware replies to keep scammers engaged. |
| 🔍 Passive Extraction | Silently captures intelligence (UPI, links, phone numbers). |
| 🔁 State-Driven Flow | Strictly manages the conversation lifecycle. |
| 📤 Verified Reporting | Triggers a single, verified callback upon conclusion. |
Each module has one responsibility and operates independently.
FraudGuard/
├── contracts/ # Interface definitions
├── receiver/ # Input validation & normalization
├── decision/ # Scam detection & state transitions
├── aiagent/ # Controlled conversational agent
├── extraction/ # Intelligence extraction
├── callback/ # Final reporting
└── orchestrator/ # System control flow
To ensure safety, FraudGuard enforces a strict execution model:
- Every session exists in one runtime state.
- Only one component controls flow at a time.
- No module acts independently.
- No uncontrolled loops.
Why? This prevents false positives, infinite engagement loops, and accidental exposure.
- System design completed
- Interfaces defined
- Implementation in progress
FraudGuard is built on a "Safety First" architecture:
- AI never controls the system.
- Decisions are explicit.
- Exits are safe.
- Reporting happens exactly once.