Back to skill

Security audit

Logscope

Security checks for vulnerabilities and agentic risk

Overview

This is an offline reference skill that prints static documentation, with minor documentation inconsistencies but no evidence of credential access, network use, persistence, or hidden behavior.

This skill is appropriate as a lightweight offline reference helper. Users should be aware it appears generic and has minor version and command-name inconsistencies, so it should not be treated as authoritative vendor 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 (2)

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 data concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

The cheatsheet says the tool supports a 'troubleshooting' command, but the dispatcher only implements 'debugging' and has no 'troubleshooting' case. This is an active documentation-to-code contradiction that can mislead users about the available interface.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.