Back to skill

Security audit

Lite Research

Security checks for vulnerabilities and agentic risk

Overview

This skill is a lightweight web-research helper with disclosed search and fetch behavior and no evidence of hidden code, persistence, credential access, or destructive actions.

Install this if you want a quick web-research shortcut. Be aware that using it will send search queries about the requested topic to web search/fetch tools, and it is not designed for exhaustive or rigorous fact-checking workflows.

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
  • 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 (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The manifest description says to use the skill when the user asks to "research" something, which is a common everyday request and may overlap with many unrelated contexts. Aside from excluding "deep research," it does not define narrower trigger boundaries or negative examples to prevent unintended invocation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The "When to Use" section defines activation as when the user says "research ", but does not specify how literal that phrasing must be or what nearby phrasings should not match. This ambiguity can cause accidental invocation from normal conversational requests involving the word "research."

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The workflow begins with "When user says "research "" but gives no extra specificity about context, intent, or matching rules. Repeating the broad trigger without constraints increases the chance of inconsistent or over-broad activation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.