Back to skill

Security audit

essesseff DevOps ALM

Security checks for vulnerabilities and agentic risk

Overview

This is a legitimate DevOps skill, but it needs review because it can drive production changes and handles powerful GitHub, Kubernetes, and app secrets with weak safeguards.

Install only if you trust the essesseff vendor and are prepared to grant the agent/operator real DevOps authority. Pin and inspect the onboarding utility before running it, use short-lived least-privilege tokens, keep kubectl pointed only at the intended cluster, require explicit confirmation for PROD deployment, package deletion, retention changes, and repository creation, and do not store .env or notifications-secret.yaml inside Git working trees.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T03 · Remote Payload Retrieval and Execution

Error
Location
references/onboarding-utility.md:14
Finding

Unpinned Remote Onboarding Scripts Are Downloaded and Executed with Privileged Credentials

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
references/onboarding-utility.md:115
Finding

GitHub and Argo CD Secrets Are Written into Git Repository Working Trees Without Effective Ignore Protection

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Findings (43)

Missing User Warnings

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill explicitly states that production deployment can be triggered through the API without OTP, yet it does not pair that capability with strong warnings or approval requirements. In a high-automation agent context, this materially raises the risk of accidental or unauthorized production changes because a single API call can promote an image directly to PROD.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · README.md (reported line 113)May include surrounding context.

md
| POST | `.../apps/{app_name}/environments/QA/declare-rejected` | Mark QA image as REJECTED |
| POST | `.../apps/{app_name}/environments/STAGING/deploy-stable` | Deploy STABLE to STAGING |
| POST | `.../apps/{app_name}/environments/PROD/deploy-stable` | Deploy STABLE to PROD (no OTP) |
| GET | `.../apps/{app_name}/notifications-secret` | Get notifications-secret.yaml for Argo CD |
| GET | `.../apps/{app_name}/packages/delete-packages` | Get expired package deletion payloads |
| GET | `.../apps/{app_name}/retention-policies` | List retention policies (filter by `?state=`) |
| PATCH | `.../apps/{app_name}/retention-policies?state={state}` | Create or update a retention policy for a lifecycle state |

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
| POST | `.../apps/{app_name}/environments/QA/declare-rejected` | Mark QA image as REJECTED |
| POST | `.../apps/{app_name}/environments/STAGING/deploy-stable` | Deploy STABLE to STAGING |
| POST | `.../apps/{app_name}/environments/PROD/deploy-stable` | Deploy STABLE to PROD (no OTP) |
| GET | `.../apps/{app_name}/notifications-secret` | Get notifications-secret.yaml for Argo CD |
| GET | `.../apps/{app_name}/packages/delete-packages` | Get expired package deletion payloads |
| GET | `.../apps/{app_name}/retention-policies` | List retention policies (filter by `?state=`) |
| PATCH | `.../apps/{app_name}/retention-policies?state={state}` | Create or update a retention policy for a lifecycle state |

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/onboarding-utility.md (reported line 144)May include surrounding context.

md
| POST | `.../apps/{app_name}/environments/QA/declare-rejected` | Mark QA image as REJECTED |
| POST | `.../apps/{app_name}/environments/STAGING/deploy-stable` | Deploy STABLE to STAGING |
| POST | `.../apps/{app_name}/environments/PROD/deploy-stable` | Deploy STABLE to PROD (no OTP) |
| GET | `.../apps/{app_name}/notifications-secret` | Get notifications-secret.yaml for Argo CD |
| GET | `.../apps/{app_name}/packages/delete-packages` | Get expired package deletion payloads |
| GET | `.../apps/{app_name}/retention-policies` | List retention policies (filter by `?state=`) |
| PATCH | `.../apps/{app_name}/retention-policies?state={state}` | Create or update a retention policy for a lifecycle state |

Credential Access

High
Category
Privilege Escalation
Confidence
96% confidence
Finding

A documented endpoint whose purpose is to retrieve a secret-bearing YAML file is inherently credential-sensitive. In a general-purpose agent skill, exposing such an endpoint without strict guidance on confirmation, redaction, and safe handling makes credential access easier to trigger and increases the chance of accidental exfiltration.

Content

Scanner excerpt · references/api-apps.md (reported line 516)May include surrounding context.

GET /accounts/{account_slug}/organizations/{organization_login}/apps/{app_name}/notifications-secret

Get notifications-secret.yaml for Argo CD setup

text
GET /api/v1/accounts/{account_slug}/organizations/{organization_login}/apps/{app_name}/notifications-secret

Credential Access

High
Category
Privilege Escalation
Confidence
98% confidence
Finding

The description explicitly states that the endpoint returns Argo CD Notifications Event Processor API keys and environment-specific app secrets, and that secrets may be automatically issued during generation. That combination expands both exposure and side effects: a read-like action not only discloses credentials but may mint new ones, magnifying abuse potential.

Content

Scanner excerpt · references/api-apps.md (reported line 524)May include surrounding context.

md
### Description

Retrieves the notifications-secret.yaml file content for Argo CD setup. Returns YAML content with `Content-Type: application/x-yaml`. This file contains Argo CD Notifications Event Processor API keys and environment-specific app secrets.

**Note:** Secrets are automatically issued from the database when this file is generated if they don't already exist.

Credential Access

High
Category
Privilege Escalation
Confidence
94% confidence
Finding

The example demonstrates downloading the secret file directly, which normalizes handling live credentials in a local artifact. In agent-driven environments, that pattern can cause secrets to be written to insecure disks, workspaces, or logs unless strong safeguards are built around file handling.

Content

Scanner excerpt · references/api-apps.md (reported line 548)May include surrounding context.

curl -X GET
"https://www.essesseff.com/api/v1/accounts/my-team/organizations/my-apps-org/apps/my-app/notifications-secret"
-H "X-API-Key: ess_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
-o notifications-secret.yaml

text

### Response

Credential Access

High
Category
Privilege Escalation
Confidence
97% confidence
Finding

The response example includes a Kubernetes Secret manifest containing an API key and multiple app secrets in plaintext stringData. Even though the values are placeholders, this documents a workflow centered on raw credential material and is dangerous in this skill context because agents may expose, copy, or persist the manifest contents.

Content

Scanner excerpt · references/api-apps.md (reported line 556)May include surrounding context.

Returns YAML content with Content-Type: application/x-yaml:

yaml
# notifications-secret.yaml

# Store Argo CD Notifications Event Processor API key and environment-specific app secrets
# ***DELETE THIS FILE AFTER APPLYING - DO NOT COMMIT SECRETS TO GITHUB***

Credential Access

High
Category
Privilege Escalation
Confidence
93% confidence
Finding

The documentation advertises an endpoint that retrieves notifications-secret.yaml, which is explicitly secret-bearing material for Argo CD setup. In an agent skill that can automate API access, exposing or normalizing retrieval of secret content materially increases the chance of credential disclosure, accidental logging, or misuse if the agent fetches and surfaces the YAML to users.

Content

Scanner excerpt · references/api-overview.md (reported line 194)May include surrounding context.

md
##### GET .../apps/{app_name}/notifications-secret

Retrieve the notifications-secret.yaml file content for Argo CD setup. Returns YAML content.

#### Other Endpoints

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/api-packages.md (reported line 19)May include surrounding context.

md
Returns GitHub API payloads for deleting package versions that correspond to expired essesseff images. The function validates that all uniquely tagged images associated with a particular GitHub package version are expired before returning the package version for deletion.

**Important:** This endpoint only returns deletion payloads. You must execute the deletion using a GitHub Personal Access Token (PAT) with appropriate permissions, as GitHub Apps cannot reliably delete package versions via the API.

### Path Parameters

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/api-packages.md (reported line 113)May include surrounding context.

md
Returns GitHub API payloads for deleting package versions that correspond to expired essesseff images. The function validates that all uniquely tagged images associated with a particular GitHub package version are expired before returning the package version for deletion.

**Important:** This endpoint only returns deletion payloads. You must execute the deletion using a GitHub Personal Access Token (PAT) with appropriate permissions, as GitHub Apps cannot reliably delete package versions via the API.

### Path Parameters

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
83% confidence
Finding

The skill documents a workflow that returns fully formed deletion payloads for package versions and then instructs callers to execute those DELETE operations against GitHub. In an agent context, this increases the risk of destructive action execution from tool-derived parameters without sufficient human confirmation, scope validation, or allowlisting, potentially causing irreversible package deletion in external repositories.

Content

Scanner excerpt · references/api-packages.md (reported line 68)May include surrounding context.

md
"organization_login": "my-apps-org",
      "repository_name": "my-app",
      "package_name": "my-app",
      "github_api_endpoint": "DELETE /repos/{owner}/{repo}/packages/{package_type}/{package_name}/versions/{package_version_id}",
      "github_api_params": {
        "owner": "my-apps-org",
        "repo": "my-app",

Credential Access

High
Category
Privilege Escalation
Confidence
96% confidence
Finding

The documentation explicitly instructs users to copy notifications-secret.yaml into a cloned Git repo during Argo CD setup. Storing or staging secret manifests in repository working trees materially increases the risk of accidental commit, push, CI exposure, or local disclosure of cluster credentials and notification secrets.

Content

Scanner excerpt · references/onboarding-utility.md (reported line 115)May include surrounding context.

md
### Argo CD Setup
For each environment:
1. (Subscribers) Downloads `notifications-secret.yaml`.
2. Clones the argocd-env repo (`{app-name}-argocd-{env}`).
3. Creates `.env` file with required variables.
4. (Subscribers) Copies `notifications-secret.yaml` to repo.

Credential Access

High
Category
Privilege Escalation
Confidence
98% confidence
Finding

The utility writes sensitive values such as GITHUB_TOKEN and Argo CD machine-user credentials into .env files inside cloned repos before running setup-argocd.sh. Even if intended for local automation, placing credentials in repo directories creates a high chance of accidental commit, leakage through shell history, editor indexing, backups, or CI/CD tooling.

Content

Scanner excerpt · references/onboarding-utility.md (reported line 118)May include surrounding context.

md
1. (Subscribers) Downloads `notifications-secret.yaml`.
2. Clones the argocd-env repo (`{app-name}-argocd-{env}`).
3. Creates `.env` file with required variables.
4. (Subscribers) Copies `notifications-secret.yaml` to repo.
5. Runs `setup-argocd.sh`.

**Variables written to `.env` files:**

Chaining Abuse

High
Category
Tool Misuse
Confidence
75% confidence
Finding

Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.

Content

Scanner excerpt · references/prerequisites.md (reported line 22)May include surrounding context.

Install on Ubuntu/Debian:

bash
sudo apt-get update && sudo apt-get install -y curl git jq
# kubectl: https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/

Credential Access

High
Category
Privilege Escalation
Confidence
80% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/prerequisites.md (reported line 56)May include surrounding context.

md
- Any K8s cluster works, including a single-VM `k3s` setup.
- Argo CD must be installed. The `setup-argocd-cluster.sh` script in this repo provides an easy way to do this.
- `kubectl` must be configured (`~/.kube/config` or `KUBECONFIG` env var) and pointing at the correct cluster for each environment **before** running `--setup-argocd`.
- The destination K8s namespace defaults to the `GITHUB_ORG` string. If your org name isn't DNS compliant or is 63+ characters, set `K8S_NAMESPACE` in `.essesseff` to a valid override.

## essesseff API Key (subscribers only)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/prerequisites.md (reported line 56)May include surrounding context.

md
- Any K8s cluster works, including a single-VM `k3s` setup.
- Argo CD must be installed. The `setup-argocd-cluster.sh` script in this repo provides an easy way to do this.
- `kubectl` must be configured (`~/.kube/config` or `KUBECONFIG` env var) and pointing at the correct cluster for each environment **before** running `--setup-argocd`.
- The destination K8s namespace defaults to the `GITHUB_ORG` string. If your org name isn't DNS compliant or is 63+ characters, set `K8S_NAMESPACE` in `.essesseff` to a valid override.

## essesseff API Key (subscribers only)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The README advertises automation for creating repositories, creating apps, and configuring Argo CD across environments without an adjacent, explicit warning that these actions change remote infrastructure and may create or modify production-facing resources. In a DevOps skill, omission of impact warnings increases the chance of accidental high-impact operations by users or downstream agents.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · README.md (reported line 70)May include surrounding context.

md
BASE=https://www.essesseff.com/api/v1

# List global templates
curl -H "X-API-Key: $ESSESSEFF_API_KEY" "$BASE/global/templates"

# Create an app
curl -X POST "$BASE/accounts/$ACCOUNT/organizations/$ORG/apps?app_name=my-app" \

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The README includes a concrete command to deploy a STABLE image to PROD but does not place a clear production-impact warning immediately around the example. In a skill that may be followed by an autonomous agent or rushed operator, this materially increases the risk of accidental production deployment, service disruption, or unapproved release activity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill documents an endpoint that returns package deletion payloads but provides no user-facing warning that acting on those payloads can remove artifacts from external registries. In an agent setting, omission of destructive-impact warnings increases the chance of unintended deletion when the model interprets the capability as routine maintenance.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The onboarding utility can create repositories, create apps, and configure Argo CD across environments, all of which modify external systems, but the documentation does not emphasize that these actions are state-changing and potentially irreversible. For an autonomous or semi-autonomous agent, that lack of warning makes unintended infrastructure changes more likely.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/api-apps.md (reported line 48)May include surrounding context.

Request Example

text
curl -X GET \
  "https://www.essesseff.com/api/v1/accounts/my-team/organizations/my-apps-org/apps" \
  -H "X-API-Key: ess_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The app-creation endpoint is documented as creating 9 repositories, setting webhooks, assigning teams, and configuring retention policies, but the docs do not emphasize that this is a high-impact side-effecting operation requiring explicit user confirmation. In an agent skill context, this omission increases the risk that an automated workflow could trigger broad infrastructure changes from an ambiguous or incomplete user request.

Content

No source excerpt is available for this finding.