srvrls-function-injctn

Detects and prevents code injection attacks targeting serverless functions (AWS Lambda, Azure Functions, Google Cloud Functions) through event source poisoning, malicious layer injection, runtime command execution, and IAM privilege escalation via function modification. The analyst combines static analysis of function code, CloudTrail event correlation, runtime behavior monitoring, and IAM policy auditing to identify injection vectors across the expanded serverless attack surface including API Gateway, S3, SQS, DynamoDB Streams, and CloudWatch event triggers. Activates for requests involving Lambda security assessment, serverless injection detection, function event poisoning analysis, or serverless privilege escalation investigation.

跳到安装

仓库: Undermybelt/hermes-skills
最近来源活动: 2026年6月7日 07:23
检测到的 SKILL.md 语言: 英语
星标: 6
分支: 1

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/Undermybelt/hermes-skills --skill srvrls-function-injctn

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

4 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

anti-entropy-governance

Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries while deciding whether to delete old paths, retain compatibility, or stop for confirmation.

2026-06-07

brainstorming

Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.

2026-06-07

communicating-concisely

Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.

2026-06-07

查看这个仓库的全部 Skills

name	srvrls-function-injctn
description	Detects and prevents code injection attacks targeting serverless functions (AWS Lambda, Azure Functions, Google Cloud Functions) through event source poisoning, malicious layer injection, runtime command execution, and IAM privilege escalation via function modification. The analyst combines static analysis of function code, CloudTrail event correlation, runtime behavior monitoring, and IAM policy auditing to identify injection vectors across the expanded serverless attack surface including API Gateway, S3, SQS, DynamoDB Streams, and CloudWatch event triggers. Activates for requests involving Lambda security assessment, serverless injection detection, function event poisoning analysis, or serverless privilege escalation investigation.
domain	cybersecurity
subdomain	cloud-security
tags	["serverless-security","Lambda-injection","event-source-poisoning","OWASP-serverless","IAM-escalation","CloudTrail"]
version	1.0.0
author	mukul975
license	Apache-2.0
nist_csf	["PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01"]

Detecting Serverless Function Injection

When to Use

Auditing Lambda/Cloud Functions for code injection vulnerabilities where unsanitized event data flows into dangerous runtime functions (eval, exec, child_process.exec, os.system)
Investigating incidents where an attacker modified function code or layers to establish persistence or exfiltrate data from the serverless environment
Detecting privilege escalation paths where an adversary with lambda:UpdateFunctionCode and iam:PassRole can assume higher-privilege execution roles
Analyzing event source poisoning attacks where malicious payloads are injected through S3 object uploads, SQS messages, DynamoDB stream records, or API Gateway requests that trigger function execution
Building detection rules for SOC teams monitoring serverless workloads for unauthorized function modifications, layer additions, and suspicious invocation patterns

Do not use for load testing or denial-of-service simulation against serverless functions, for testing against production functions processing live customer data without explicit authorization, or for modifying IAM policies in shared accounts without change management approval.

Prerequisites

AWS account access with read permissions for Lambda, CloudTrail, IAM, CloudWatch Logs, and EventBridge
AWS CLI v2 configured with appropriate credentials and region
CloudTrail enabled with Data Events for Lambda (captures Invoke events) and Management Events (captures UpdateFunctionCode, UpdateFunctionConfiguration, CreateFunction)
Python 3.9+ with boto3, bandit (Python SAST), and semgrep for static analysis
Access to function source code or deployment packages for static analysis
CloudWatch Logs Insights access for querying Lambda execution logs

Workflow

Step 1: Enumerate the Serverless Attack Surface

Map all Lambda functions and their event source triggers to understand injection entry points:

List all Lambda functions and their configurations:

aws lambda list-functions --query 'Functions[*].[FunctionName,Runtime,Role,Handler,Layers]' --output table

Map event source mappings: Each event source mapping is a potential injection entry point where untrusted data enters the function:

Term	Definition
Event Source Poisoning	An attack where malicious data is injected into a serverless event source (S3, SQS, DynamoDB Stream, API Gateway) to trigger code execution or injection when the function processes the event
Function Injection	Exploitation of unsanitized event data that flows into dangerous runtime functions (eval, exec, os.system, child_process.exec) within a serverless function handler
Lambda Layer Hijacking	An attack where a malicious Lambda layer is attached to a function to intercept execution, override dependencies, or exfiltrate data by placing code in the runtime's module search path
IAM Privilege Escalation via Lambda	A technique where an attacker with UpdateFunctionCode and PassRole permissions modifies a function to execute with a higher-privilege IAM role, extracting temporary credentials
OWASP Serverless Top 10	A security framework identifying the ten most critical risks in serverless architectures, including injection (SAS-1), broken authentication (SAS-2), and over-privileged functions (SAS-6)
Cold Start Injection	An attack that targets the function initialization phase where environment variables, layer code, and extensions execute before the handler, potentially in an unmonitored context
Execution Role	The IAM role assumed by a Lambda function during execution, providing temporary credentials that define the function's AWS API access permissions

srvrls-function-injctn

安装方式

检查来源文件

Detecting Serverless Function Injection

When to Use

Prerequisites

Workflow

Step 1: Enumerate the Serverless Attack Surface

Detecting Serverless Function Injection

When to Use

Prerequisites

Workflow

Step 1: Enumerate the Serverless Attack Surface

Step 2: Static Analysis for Injection Sinks

Step 3: Detect Event Source Poisoning

Step 4: Detect Malicious Lambda Layer Injection

Step 5: Detect IAM Privilege Escalation via Lambda

Step 6: Implement Runtime Injection Prevention

Key Concepts

Tools & Systems

Common Scenarios

Scenario: Detecting and Responding to a Lambda-Based Privilege Escalation Attack

Output Format

srvrls-function-injctn

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Detecting Serverless Function Injection

When to Use

Prerequisites

Workflow

Step 1: Enumerate the Serverless Attack Surface

Detecting Serverless Function Injection

When to Use

Prerequisites

Workflow

Step 1: Enumerate the Serverless Attack Surface

Step 2: Static Analysis for Injection Sinks

Step 3: Detect Event Source Poisoning

Step 4: Detect Malicious Lambda Layer Injection

Step 5: Detect IAM Privilege Escalation via Lambda

Step 6: Implement Runtime Injection Prevention

Key Concepts

Tools & Systems

Common Scenarios

Scenario: Detecting and Responding to a Lambda-Based Privilege Escalation Attack

Output Format