Back to skill

Security audit

Logrotate

Security checks for vulnerabilities and agentic risk

Overview

This skill is a static logrotate-themed reference command with no evidence of credential access, network calls, persistence, or destructive behavior, but its documentation is generic and not reliable as real logrotate guidance.

Installing this appears low-risk from a security perspective, but use it only as generic sysops notes. Do not rely on it for production logrotate configuration or troubleshooting without checking authoritative logrotate documentation.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The code is benign and primarily serves documentation/reference output, which is broadly aligned with a reference-tool description. However, the declared purpose specifically says it is a devtools reference tool for Logrotate concepts, best practices, and implementation patterns. The actual code is a standalone bash command that emits mostly generic, boilerplate sysops guidance with 'Logrotate' inserted, rather than meaningful Logrotate-specific reference content. This makes the represented subject matter materially inaccurate. It also includes several extra documentation sections beyond the stated intro/quickstart/patterns scope. So while the high-level category (reference/help tool) matches, the description does not accurately represent what the code truly delivers.

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 · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of sysops concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The inline header explicitly presents the script as a Logrotate reference tool, but the implementation does not substantively document Logrotate. In a reference skill, this mismatch undermines trust and can lead operators to apply generic or incorrect sysops advice where precise Logrotate behavior matters.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The script claims to be a Logrotate reference tool, but nearly all content is a generic sysops template with no Logrotate-specific commands, configuration syntax, rotation policies, or operational guidance. This is dangerous because users may rely on it for administrative decisions and receive misleading or incomplete guidance, increasing the chance of misconfiguration in production environments.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.