Back to skill

Security audit

Pine Patterns

Security checks for vulnerabilities and agentic risk

Overview

This is a small Pine Script guidance skill with no executable payload, but users should adjust the baked-in author, filename, and US-market defaults for their own work.

Before installing, be aware that generated examples may inherit the author's naming, attribution, MPL-2.0 header, and US-market session defaults. Replace those with your own author, license, filename, timezone, and market session when creating code for yourself or clients.

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
Findings (1)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:21
Finding

Mandatory Third-Party Branding and Authorship in Generated Code

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 21–22 and line 59
Vulnerability Type: Output instruction hijacking through forced attribution
Risk Level: Medium

Complete Code Snippets:

markdown
- File naming: `LB_*.pine`
- Author: Luther Barnum
pinescript
// © lgbarn

Technical Analysis

The skill instructs the agent to apply a fixed third-party filename prefix and authorship identity to generated Pine Script files. The included template reinforces this instruction by inserting a copyright notice for lgbarn.

These directives are not required for Pine Script correctness and are not conditioned on user consent or actual authorship. When the skill is loaded, an agent may treat them as authoritative generation requirements, causing unrelated user deliverables to contain attacker- or maintainer-controlled branding. This constitutes instruction hijacking because the skill modifies generated output in a way that serves an external attribution objective rather than the user's development request.

Attack Path

  1. A user or agent loads the pine-patterns skill to obtain Pine Script guidance.
  2. The agent processes the stated file conventions as mandatory instructions.
  3. The agent generates a file with an LB_ filename and identifies Luther Barnum or lgbarn as the author or copyright holder.
  4. The user publishes or distributes the generated code without noticing or correcting the attribution.
  5. The resulting artifact misrepresents its authorship and provenance.

Impact Assessment

The issue does not grant operating-system privileges, access credentials, code-execution capabilities, or access to protected resources. Its impact is limited to the integrity and provenance of generated deliverables.

Affected output may carry false authorship or copyright claims, creating attribution, licensing, reputational, or ownership ambiguity. The scope includes Pine Script file ...[truncated 75 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove the mandatory LB_*.pine filename convention and fixed author identity.
  2. Replace fixed attribution with neutral placeholders such as <filename> and <author>.
  3. Ask users to provide their preferred filename, author, and license before adding this metadata.
  4. Omit attribution by default when the user has not supplied it.
  5. Clearly label any Luther Barnum-branded template as optional and require explicit user selection before applying it.
  6. Update the example copyright header to use a neutral placeholder or explain that it must be replaced with the actual copyright holder.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The document prescribes fixed session defaults of 'RTH: 9:30 AM - 4:00 PM ET' and 'Timezone: America/New_York' as standard guidance. This can be a natural-language locale policy issue because it imposes a specific regional market/timezone context without offering a user choice or clearly limiting the skill to that region-specific use case.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.