Back to skill

Security audit

SIFS Search: Fast hybrid code search for agents

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed SIFS-based code search helper, with the main caution being its unpinned third-party CLI dependency.

Install this only if you trust the SIFS package source. Prefer a pinned or verified SIFS release when possible, run it only against source trees you intend to index or inspect, and preview any generated agent instructions before using force install commands.

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

Unpinned Third-Party Executable Dependency

Content
View full analysis
Remediation
View remediation
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 (1)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The declared description is for a code-search/discovery skill operating over a local checkout or Git source. The supplied code does not search code, inspect repositories, or locate symbols/files/implementations. Instead, it checks whether the sifs command exists on PATH, prints install instructions if absent, and runs version/context commands as a readiness test. That is a materially different primary purpose, so this is a clear description-behavior mismatch.

Content

No source excerpt is available for this finding.