YouTube 批量发布器

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward YouTube uploader, but it needs careful handling because it can publish account content and stores a reusable OAuth token locally.

Install only if you intend to let this tool upload videos to the chosen YouTube account. Replace the placeholder OAuth file with your own Google Cloud client, verify the account and privacy setting before each upload, protect or delete credentials/token.pickle after use, and revoke the Google app access when finished.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The README advertises bulk video uploads, metadata edits, thumbnail changes, and privacy-setting control without warning users that the tool can make large-scale, account-affecting changes. In an agent skill context, this omission is risky because users may authorize the skill without understanding that it can publicly publish, modify, or misconfigure many videos at once.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill instructs users to supply OAuth credentials and upload local video and thumbnail files, but it does not explicitly warn that these files and associated metadata will be transmitted to YouTube/Google services. This is a real security/privacy documentation issue because users may unknowingly expose sensitive content or account-linked data to a third party.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The code persists OAuth credentials to a local pickle file on disk without any permission hardening, encryption, or user warning. OAuth refresh tokens are sensitive authentication material; if another local user, process, backup system, or malware can read or replace this file, it can enable account access or token theft, and using pickle also adds unsafe deserialization risk if the file is tampered with.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal