ClawHub

Umask Tool

Security checks across malware telemetry and agentic risk

Overview

This umask utility is small and not visibly malicious, but it silently changes file-permission behavior while its documentation says it can simply display the current setting.

Review before installing or invoking. A safer version should separate show and set modes, restore the old umask when only displaying it, require and validate an explicit mask before changing permissions, and document whether any change affects only a subprocess or the agent's longer-lived environment.

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 (2)

Description-Behavior Mismatch

Medium
Confidence
99% confidence
Finding
The script calls os.umask(0) inside print(), which does not merely display the current umask: it sets the process umask to 0 and returns the previous value. This leaves the current process and any child operations creating files with maximally permissive defaults, which can cause newly created files or directories to become overly accessible.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
Changing the process umask without warning is dangerous because users would reasonably expect a 'display' utility to be side-effect free. In the context of a skill advertised as controlling default file permissions, silently setting the umask to 0 makes subsequent file creation less secure and increases the chance of world-readable or world-writable artifacts.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal