Menu

Individual skill

s3-takeover

0upvotes

Detect and claim dangling S3 buckets referenced by subdomains (CNAME → s3 hostnames where bucket no longer exists).

packages/decepticon/decepticon/skills/standard/cloud/s3-takeover/SKILL.md

Read pinned source

Source commit df879550544d36b6b1e69062f05adae28537adf2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,568
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# S3 Subdomain Takeover

When a subdomain has a `CNAME` to an S3 hostname (e.g.
`assets.example.com → assets-example.s3.amazonaws.com`) but the bucket
no longer exists, **anyone can register that bucket name and serve
content from the subdomain**.

## 1. Enumerate subdomains pointing at S3
From recon SUMMARY.md, look for any CNAME containing:
- `s3.amazonaws.com`
- `s3-website-<region>.amazonaws.com`
- `s3.<region>.amazonaws.com`
- `s3-website.<region>.amazonaws.com`
- `<bucket>.s3.<region>.amazonaws.com`