Back to skill

Security audit

Graylog Log Search

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Graylog log-search integration, but it combines production log access and API-token use with broad triggers and unverified npm execution.

Install only if you trust the npm package and publisher, can verify the package source or integrity, and can use a dedicated read-only Graylog token with limited stream/search permissions. Avoid enabling the broad triggers unless they are renamed or scoped so generic debugging prompts do not access production logs.

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:29
Finding

Unaudited Third-Party npm Package Executes with Production Graylog Credentials

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Shadow Command Trigger

Medium
Category
Trigger Abuse
Confidence
88% confidence
Finding

The trigger 'log search' can shadow or collide with a built-in 'log' command namespace, creating ambiguity in routing. If the agent selects this skill when the user intended a different logging command, it could query production Graylog data unexpectedly and broaden access beyond user intent.

Content

No source excerpt is available for this finding.

Shadow Command Trigger

Medium
Category
Trigger Abuse
Confidence
86% confidence
Finding

The trigger 'debug logs' overlaps conceptually with a built-in 'debug' command family and is likely to create invocation ambiguity. In this context, ambiguity is more dangerous because the skill reaches production log data, so a mistaken dispatch can reveal sensitive telemetry or incident details.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The trigger phrase 'production debugging' is broad enough to activate in many operational conversations that are not explicitly requesting Graylog access. Because this skill enables searches against production logs, accidental invocation could expose sensitive operational or application data to a workflow that did not intend to access it.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
85% confidence
Finding

The trigger 'debug logs' is highly generic and may match routine debugging requests across many contexts. In a skill that connects to production logging infrastructure, this increases the chance of unintended tool execution and unnecessary access to potentially sensitive log contents.

Content

No source excerpt is available for this finding.