D068F3
SaaS
📂 Honey Code Repository
Fake GitHub/GitLab repos with embedded honeytokens.
What it is
Create fake internal repositories with attractive names (infrastructure-secrets, prod-terraform-state) containing planted honeytokens. When cloned or accessed, the embedded tokens alert on use.
Implementation requirements
- GitHub/GitLab organization with repo creation permissions
- Realistic commit history (use scripts to generate months of fake commits)
- Embedded honeytokens: AWS keys, API tokens, database connection strings
- GitHub audit log monitoring for clone/access events
- Rollback: Archive or delete the repository and revoke its embedded tokens; check for forks and mirrors.
- Upkeep: Add commits occasionally so it does not look abandoned. Monthly proof-of-life clone.
Technologies
AWSCI/CD
ATT&CK coverage 2
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1213.003 Code Repositories |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (4 sources)
| ||||
| T1552.001 Credentials In Files |
Credential Access | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (5 sources)
| ||||
Evidence
- SaaS Attack Techniques — Push Security industry
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
Research basis: Push Security, "SaaS Attack Techniques" (Industry Research). Thinkst Canaries documentation on code repository tokens.