Back to skill

Security audit

Backup Rotator

Security checks across malware telemetry and agentic risk

Overview

This is a local backup utility whose file creation, rotation, deletion, and optional cron use are disclosed and aligned with its purpose, though users should treat rotation as destructive and verification as checksum reporting rather than full restore validation.

Install only if you want a local tool that can delete old backup files according to retention rules. Use --dry-run and --list before real rotation, keep backups in a dedicated directory, choose a narrow --name prefix, and do not rely on the SHA256 output as proof that a backup is restorable.

SkillSpector

By NVIDIA
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 (4)

Intent-Code Divergence

Medium
Confidence
95% confidence
Finding
The function claims to verify backup integrity, but it only computes and prints a checksum or checks for empty files; it does not compare against a previously trusted checksum, manifest, or source content. This can mislead operators into believing backups are validated when corruption, truncation, or tampering may go undetected.

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
After backup creation, the code labels the step as verification but merely hashes the produced artifact and reports its size. Without comparing that hash to an expected value or validating archive readability/content, this provides no assurance that the backup is correct or restorable.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The description advertises automatic cleanup of old backups but does not prominently warn that rotation permanently deletes files based on policy. In a backup tool, users may assume cleanup is safe by default, so omission of an irreversibility warning can lead to unintended data loss.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The cron example schedules unattended execution of backup and rotation, which can automatically delete backup files on every run without any visible warning in the automation section. Because cron jobs run repeatedly and silently, configuration mistakes or unexpected prefix/path matching can cause recurring data loss before an operator notices.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.