Back to skill

Security audit

Security Plus

Security checks for vulnerabilities and agentic risk

Overview

This is a security reference skill with purpose-aligned scanning and hardening commands, but users should review external tool commands before running them.

Install only if you want a security-checklist and tooling reference. Before running its example commands, pin tool versions where possible, review changes from npm audit fix, run scanners only against systems you are authorized to test, and avoid running external tooling with production credentials present.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:173
Finding

Unpinned Third-Party Tools and Mutable Remote Hook References

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 173-204
Vulnerability Type: Supply-chain exposure through unpinned third-party dependencies
Risk Level: Medium

Vulnerable Code

bash
# npm audit
npm audit
npm audit fix

# Snyk
npx snyk test
npx snyk monitor

# Safety (Python)
safety check

# Bundler-audit (Ruby)
bundle-audit check --update
bash
# Install pre-commit
pip install pre-commit

# Add to .pre-commit-config.yaml
repos:
  - repo: https://github.com/Yelp/detect-secrets
    rev: v1.4.0
    hooks:
      - id: detect-secrets
        args: ['--baseline', '.secrets.baseline']

Technical Analysis

The skill recommends downloading or executing third-party tooling without integrity verification or immutable version constraints:

  • npx snyk does not specify an exact package version. If the package is unavailable locally, npx may download and immediately execute the version resolved from the configured npm registry.
  • pip install pre-commit does not pin a version or require package hashes.
  • The detect-secrets hook is pinned to the Git tag v1.4.0, not an immutable commit SHA. Repository tags can potentially be moved or replaced by a compromised maintainer account.
  • npm audit fix can change dependency resolution and install updated packages without requiring a manual review of each proposed change. Package installation may also invoke lifecycle scripts where permitted.

These practices create a supply-chain trust boundary in which the code ultimately executed can differ from the code previously reviewed. The file does not itself contain a malicious payload, but following its instructions could execute compromised registry or repository content.

Attack Path

  1. An attacker compromises a referenced package, package-publisher account, registry resolution path, or upstream repository.
  2. The attacker publishes a malicious package versio ...[truncated 1091 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin every package to an exact, reviewed version, such as npx snyk@<exact-version>, and configure npx to avoid unintended implicit downloads where practical.
  2. Install Python tools from a reviewed lock file with exact versions and hashes, using mechanisms such as pip install --require-hashes -r requirements.txt.
  3. Pin pre-commit repositories to reviewed immutable commit SHAs rather than tags or branches.
  4. Commit lockfiles and verify their integrity in CI before installation.
  5. Run package installation and security tools in an isolated, least-privileged environment without production credentials.
  6. Run npm audit fix --dry-run first, review the proposed dependency and lockfile changes, and test them before applying the update.
  7. Disable package lifecycle scripts when they are unnecessary, or explicitly review packages that require them.
  8. Use trusted registries, package provenance verification, and internal mirrors where appropriate.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

YARA rule 'offensive_tool_references': References to well-known offensive security tools [hacktools]

High
Category
YARA Match
Confidence
70% confidence
Finding

YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).

Content

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

irections

  • Segment networks
  • Use metadata endpoints
text

## Vulnerability Scanning

### SAST (Static Application Security Testing)

```bash
# SonarQube
sonar-scanner

# Semgrep
semgrep scan --config=auto

# Bandit (Python)
bandit -r src/

DAST (Dynamic Application Security Testing)

bash
# OWASP ZAP
docker run -t owasp/zap2docker-stable zap-baseline.py -t https://example.com

# Nikto
nikto -h https://example.com

Dependency Scanning

bash
# npm audit
npm audit
npm audit fix

# Snyk
npx snyk test
npx snyk monitor

# Safety (Python)
safety check

# Bundler-audit (Ruby)
bundle-audit check --update

Secrets Detection

Pre-commit Hooks

bash
# Install pre-commit
pip install pre-commit

# Add to .pre-commit-config.yaml
repos:
  - repo: https://github.com/Yelp/detect-secrets
    rev: v1.4.0
    hooks:
      - id: detect-secrets
        args: ['--baseline', '.secrets.baseline']

Scanning Tools

bash
# detect-secrets
detect-secrets scan

# gitlea

Rp1

Medium
Category
MCP Rug Pull
Confidence
88% confidence
Finding

The Docker example uses owasp/zap2docker-stable without a specific tag or digest, so users may pull different image contents over time. That creates supply-chain and reproducibility risks, including exposure to a compromised or unexpectedly changed image when the command is executed.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
92% confidence
Finding

The skill recommends running npx snyk without pinning a version, which can cause users to fetch and execute whatever package version is current at runtime. This introduces a supply-chain risk: a compromised upstream release or unexpected breaking change could execute untrusted code in the user's environment.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
92% confidence
Finding

This second npx snyk invocation has the same issue: it relies on an unpinned package version resolved at execution time. In a security-focused skill, asking users to run unpinned remote tooling is especially risky because it normalizes executing external code with trust assumptions that may not hold.

Content

No source excerpt is available for this finding.