Menu

Individual skill

attacking-serverless

0upvotes

Attack serverless compute — AWS Lambda, Azure Functions, GCP Cloud Functions, and edge runtimes like Cloudflare Workers. Enumerate functions, inject through event sources (S3, SQS, SNS, API Gateway, EventBridge), extract credentials from the execution environment, abuse over-privileged IAM roles, exploit cold-start persistence and container reuse, and test trigger misconfigurations. Use when a target runs serverless functions, when API Gateway or function URLs front compute, when event-driven architectures process untrusted input, or when cloud function execution roles need privilege-escalation testing.

secskills-offense/skills/attacking-serverless/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

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 6, 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)
188
Repository last updated
Sep 4, 2026
License
MIT

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

# Attacking Serverless

Serverless changes the attack surface from hosts to events. There is no SSH, no
persistent shell, no OS to enumerate in the traditional sense. The execution
environment is ephemeral, but the IAM role attached to it is not, and that role
is almost always the real target. A compromised Lambda function does not give you
a server — it gives you a set of AWS credentials that refresh automatically,
have no MFA, and were scoped by a developer who optimized for "make it work"
rather than least privilege. The same pattern holds across Azure Functions, GCP
Cloud Functions, and edge runtimes, with minor variation in where the credentials
live and how the isolation boundary is drawn.

## When to Use
Back to top