Back to skill

Security audit

AWS STS

Security checks for vulnerabilities and agentic risk

Overview

This AWS STS skill is mostly coherent, but it can obtain temporary cloud credentials and includes unsafe remote installer commands without enough user-control safeguards.

Review this carefully before installing. It is intended to operate AWS STS through an OOMOL-connected account, so only use it where returning temporary AWS credentials to the agent is acceptable. Prefer installing the oo CLI through a verified package or reviewed installer path rather than running the pipe-to-shell commands directly.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The skill instructs users to install software via a remote script piped directly into a shell (curl ... | bash), which executes unverified code fetched at runtime. If the distribution endpoint, transport chain, or served script is compromised, this can lead to arbitrary code execution on the host running the command.

Content

Scanner excerpt · SKILL.md (reported line 56)May include surrounding context.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The phrase "Use this skill for ANY AWS STS request" is very broad and does not define trigger boundaries, exclusions, or negative examples. This can cause unintended invocation whenever AWS STS is mentioned, even if the user did not intend to run this specific skill.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.