Back to skill

Security audit

Noise Maker

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed planning document for an alert gateway skill, with no bundled executable code or hidden behavior found.

Before installing or building from this skill, confirm which parts are actually implemented, keep HMAC validation enabled for alert sources, review any scripts that can close incidents or toggle rules, and require human approval before enabling LLM-driven suppression.

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
  • 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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

L003 states 'implementation not started', yet later sections describe the skill structure, specific scripts such as close_incident.sh and toggle_rule.sh, startup hook behavior, and gateway writes into the skill directory. This is an active contradiction in the document's stated implementation state rather than a mere omission.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

L069 says the LLM filter is passive-first and activates after 50–100 alerts, and L413 explicitly says to skip LLM for the initial build. However, L042 and L095 depict the LLM as part of the live processing chain for edge-case alert decisions, which contradicts the later implementation note.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.