<!-- Copyright (c) 2026 defconxt. All rights reserved. -->
<!-- Licensed under AGPL-3.0 — see LICENSE file for details. -->
<!-- NERF is a trademark of defconxt. -->
---
name: conducting-baiting-attack-simulations
description: >-
  Design and execute baiting attack simulations using physical media and digital lures to test employee security awareness.
domain: cybersecurity
subdomain: social-engineering
tags:
  - baiting
  - usb-drop
  - digital-lures
  - physical-media
  - awareness-testing
version: "1.0"
author: defconxt
license: AGPL-3.0
metadata:
  mitre-attack: ["T1091"]
  cwe: ["CWE-693"]
  tools: ["usb-rubber-ducky", "bash-bunny", "canary-tokens"]
---

# Conducting Baiting Attack Simulations

## Overview

Design and execute baiting attack simulations using physical media and digital lures to test employee security awareness.

## Prerequisites

| Tool / Requirement | Details |
|---|---|
| `usb-rubber-ducky` | Security tooling |
| `bash-bunny` | Security tooling |
| `canary-tokens` | Security tooling |
| Isolated lab environment for testing | Environment requirement |
| Authorization and signed Rules of Engagement (RoE) | Environment requirement |
| Relevant target samples or systems acquired through authorized channels | Environment requirement |

## Quick Reference

```bash
# Initialize working environment
mkdir -p /tmp/conducting-baiting-attack-simulations/{output,logs,artifacts}

# Execute primary analysis with usb-rubber-ducky
echo "[*] Running Conducting Baiting Attack Simulations with usb-rubber-ducky..."

# Validate results with bash-bunny
echo "[*] Cross-validating with bash-bunny..."

# Generate summary report
cat /tmp/conducting-baiting-attack-simulations/output/report.json
```

## Workflow

### Step 1: Preparation and Reconnaissance

```bash
# Identify target and gather initial intelligence
file ./target_sample
usb-rubber-ducky --version 2>/dev/null || echo "Install usb-rubber-ducky"

# Set up working directory
mkdir -p /tmp/conducting-baiting-attack-simulations/{output,logs,artifacts}
```

### Step 2: Primary Analysis

```bash
# Execute primary analysis with usb-rubber-ducky
# Refer to Quick Reference above for detailed commands
echo "[*] Running Conducting Baiting Attack Simulations with usb-rubber-ducky..."

# Log all operations
script -q /tmp/conducting-baiting-attack-simulations/logs/session.log
```

### Step 3: Deep Investigation

```bash
# Apply bash-bunny for secondary analysis
echo "[*] Deep investigation with bash-bunny..."

# Cross-reference findings
diff /tmp/conducting-baiting-attack-simulations/output/primary.json /tmp/conducting-baiting-attack-simulations/output/secondary.json
```

### Step 4: Documentation and Reporting

```bash
# Generate structured findings report
cat <<'EOF' > /tmp/conducting-baiting-attack-simulations/output/report.json
{
  "technique": "conducting-baiting-attack-simulations",
  "domain": "social-engineering",
  "tools_used": ["usb-rubber-ducky", "bash-bunny"],
  "findings": [],
  "recommendations": []
}
EOF
```

## Verification

- [ ] Environment and tools verified and operational
- [ ] Target samples acquired through authorized channels
- [ ] Primary analysis completed with findings documented
- [ ] Secondary validation performed with independent tooling
- [ ] All artifacts preserved in structured output directory
- [ ] Detection opportunities documented for blue team

## References

- [MITRE ATT&CK T1091](https://attack.mitre.org/techniques/T1091) — Related technique
- [usb-rubber-ducky Documentation](https://usb-rubber-ducky.org/) — Primary tooling
- [bash-bunny Reference](https://bash-bunny.org/) — Secondary tooling
