Back to skill

Security audit

FITS Log

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marked this skill benign because its reported FITS-file scanning purpose appears coherent and no other issues were reported, though the install command triggered a low-probability scanner match and coverage was partial.

If you install it, review the GitHub source and its dependencies first. The scan covered the listed Markdown component, but completeness was marked partial because two local path-like references could not be resolved; treat the verdict as informative rather than a guarantee of safety.

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 21)May include surrounding context.

g

What this tool does

fitslog scans a folder tree of FITS files — headers only, image data is never loaded — and writes one night-log CSV with the same columns for every file, normalising the keyword spellings different instruments use for the same thing. A second, optional audit CSV flags the problem files: corrupt files, missing fields, duplicated keywords, no WCS.

Install

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

This provides the fitslog command.

Run

bash
fitslog scan /data/night1 --out nightlog.csv --audit audit.csv
  • The scan recurses all subfolders. Files ending in .fits, .fit or .fts (any case) are scanned, including compressed forms (.fits.gz, .bz2, .xz, fpack .fits.fz).
  • --audit is optional; the printed summary and flagged-file list appear either way.
  • One row per file appears in the night log — including corrupt files, which get a mostly-empty row and an audit entry. A corrupt file never stops th