Back to skill

Security audit

ICS Lint

Security checks for vulnerabilities and agentic risk

Overview

The verdict is benign: scanners found no confirmed malicious behavior, while flagging a Git-based pip install command; the review has medium confidence and incomplete coverage because a referenced example file was missing.

Consider that installation uses pip to fetch a Git-hosted package. The scan covered the listed skill file, but a referenced example file was missing, so evidence is incomplete; benign does not mean risk-free.

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
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • 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)

YARA rule 'agent_skill_remote_bootstrap_execution': Remote script or code download followed by execution/bootstrap installation [agent_skills]

High
Category
YARA Match
Confidence
85% confidence
Finding

YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).

Content

Scanner excerpt · SKILL.md (reported line 17)May include surrounding context.

RRULE syntax and form cross-checks, and TEXT escaping. Every finding names the file, the physical line, the component, the rule ID, the severity, a plain-language explanation, and its source: an RFC 5545 section, or a named, dated importer source labelled "Importer behaviour" — the two are never blended silently. It reports only; it never edits, fixes or converts the file.

Install

bash
pip install git+https://github.com/RakTikoo/icslint

This provides the icslint command.

Run

Check one file, or a folder (scanned recursively for *.ics files):

bash
icslint check examples/broken.ics
icslint check path/to/calendars --format json

--format json emits the same findings as JSON for CI tooling. --strict makes warnings fail the run as well as errors.

Reading the results

Findings print one per line: file:line: ERROR|WARNING RULE-ID [COMPONENT[UID=...]] explanation (source). The last line is the tally, printed with real singular/plural forms and both cou