Back to skill

Security audit

Github Trending

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small, disclosed GitHub Trending fetcher that does not show hidden persistence, credential access, or unrelated behavior.

Installers should expect this skill to make outbound requests to public GitHub Trending pages and display timestamps in UTC+8 with English-preferred fetched content. It does not require credentials or package installs.

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
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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 (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
89% confidence
Finding
The skill documents and encourages network access to fetch data from GitHub, but it declares no explicit tool scope or permissions boundary. In an agent environment, undeclared network capability can bypass least-privilege controls, making it harder for operators to review, sandbox, or restrict outbound access and increasing the risk of unintended data egress or misuse if the skill is invoked in broader contexts.

Natural-Language Policy Violations

Low
Confidence
94% confidence
Finding
The markdown explicitly states that time is displayed in Beijing time (UTC+8). This is a locale choice presented as fixed behavior, and the file does not offer user opt-in or explain that the skill is intended only for a China-specific audience.

Natural-Language Policy Violations

Low
Confidence
91% confidence
Finding
The HTTP request hard-codes the `Accept-Language` header to `en-US,en;q=0.9`, which forces a specific language/locale preference for fetched content. This is a natural-language policy concern because the skill does not offer the user any language choice or explain why English is required.

Static analysis

No suspicious patterns detected.