Back to skill

Security audit

maothinking

Security checks for vulnerabilities and agentic risk

Overview

This is a small local Python toolkit for Mao-themed problem analysis and decision prompts, with no hidden network, credential, persistence, or destructive behavior found.

Install only if you are comfortable with a mostly Chinese-language, Mao-themed decision-analysis toolkit. Avoid treating its scoring or strategic labels as authoritative for high-stakes personal, business, legal, medical, or financial decisions, and pin or audit the optional development dependencies before using them in CI.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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
Findings (19)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

The document includes a bilingual title, but the installation, usage instructions, examples, and section content are primarily in Chinese. This can impose a specific language on users without explicitly offering an alternative locale or documenting that the skill is intended only for Chinese-speaking users.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

This Python skill's user-facing documentation and command descriptions are entirely in Chinese, establishing a fixed language for interaction without any indication of user opt-in or alternative locale support. The policy explicitly calls out language or locale constraints as violations when a skill forces a specific language without user choice.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This code file contains natural-language instructions, examples, and descriptions only in Chinese, which effectively forces a specific language for users. The policy allows locale constraints only when users are given a choice or when the constraint is clearly justified, neither of which is present here.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This code file contains natural-language instructions, commands, and examples only in Chinese, which effectively forces a specific language for use. The policy allows locale constraints only when the skill offers opt-in or clearly documents a justified region/language limitation, neither of which is present here.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

This setup file embeds a Chinese-language title and branding in the package metadata alongside an English translation, but provides no indication that language or locale is optional or region-specific. Under the policy for natural-language violations, forcing a specific language or locale without user opt-in should be flagged when not clearly justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill description, headings, examples, and usage instructions are entirely in Chinese, and the file does not offer any language or locale choice for users. Under the policy, a skill that effectively enforces a specific language without opt-in can be a natural-language policy violation unless the restriction is explicitly justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The manifest description is written only in Chinese, which can function as a language constraint for users discovering or invoking the skill. The file does not indicate any language choice, multilingual support, or explicit justification for limiting the skill to Chinese-speaking users.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

This file presents the skill name and exported description primarily in Chinese, including the package description string, without any indication that language selection is optional or that the skill is intended only for a Chinese-language audience. Under the policy, forcing a specific language or locale without opt-in can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This code file contains natural-language instructions and examples only in Chinese, which effectively forces a specific language for users interacting with the skill. The policy allows locale constraints when users are given a choice or the restriction is explicitly justified, neither of which appears here.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The module docstring, usage examples, argument descriptions, and output labels are all written exclusively in Chinese, with no indication that users may choose another language. This creates a language/locale constraint in the skill's natural-language interface without explicit opt-in or justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

This code file contains user-facing natural language that forces a specific language/locale for all interactions. Under the policy, language constraints should either be optional for the user or clearly documented as justified for a region-specific tool.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

The comments present the skill identity and usage context in Chinese, with only partial English duplication, which indicates a language-specific presentation. For a general-purpose skill file, this can violate language/locale policy when no user opt-in or explicit region-specific justification is provided.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
93% confidence
Finding

Using an unpinned version range for pytest allows different environments to resolve different releases over time, which can introduce vulnerable or incompatible versions without review. Although pytest is listed as a development dependency, supply-chain risk remains because CI, local development, or test automation may install an unsafe release.

Content

Scanner excerpt · requirements.txt (reported line 8)May include surrounding context.

text
# Python 3.7+ 标准库即可运行

# 开发依赖(可选)
pytest>=6.0
pytest-cov>=3.0
black>=22.0
flake8>=4.0

Unverifiable Dependency: pytest has 2 known advisory(ies) (CVE-2025-71176 (pytest has vulnerable tmpdir handling); CVE-2025-71176 (pytest has vulnerable tmpdir handling)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
88% confidence
Finding

The manifest references pytest without pinning a version, and known advisories exist for some pytest releases, making it impossible to verify whether installed environments are affected. This uncertainty is itself a supply-chain weakness because a vulnerable version could be pulled in silently during development or CI.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
93% confidence
Finding

An unpinned pytest-cov dependency permits non-deterministic installation of future releases, increasing supply-chain and reproducibility risk. Even as a dev dependency, it can affect CI pipelines and developer environments where malicious or vulnerable versions may be introduced.

Content

Scanner excerpt · requirements.txt (reported line 9)May include surrounding context.

text
# 开发依赖(可选)
pytest>=6.0
pytest-cov>=3.0
black>=22.0
flake8>=4.0
mypy>=0.950

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
96% confidence
Finding

The black dependency is unpinned, so installs may resolve to different versions over time, including releases with known security issues. Because formatters are often run automatically in CI or editor integrations on untrusted repositories, a vulnerable version can create a more meaningful attack surface than a purely passive library.

Content

Scanner excerpt · requirements.txt (reported line 10)May include surrounding context.

text
# 开发依赖(可选)
pytest>=6.0
pytest-cov>=3.0
black>=22.0
flake8>=4.0
mypy>=0.950

Unverifiable Dependency: black has 5 known advisory(ies) (CVE-2026-32274 (Black: Arbitrary file writes from unsanitized user input in cache file name); CVE-2024-21503 (Black vulnerable to Regular Expression Denial of Service (ReDoS)); CVE-2024-21503 (Versions of the package black before 24.3.0 are vulnerable to Regular Expression) +2 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
95% confidence
Finding

Black has known advisories for some versions, but the dependency is not pinned, so the manifest cannot prove that a safe release will be installed. Because developer tools like black may process untrusted repositories or run in automation, unresolved exposure to vulnerable versions can have practical security impact.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
92% confidence
Finding

An unpinned flake8 dependency allows drift to unreviewed versions, which weakens build reproducibility and can expose development tooling to supply-chain issues. While the runtime impact is limited because this is a dev dependency, automated CI use still makes version control important.

Content

Scanner excerpt · requirements.txt (reported line 11)May include surrounding context.

text
pytest>=6.0
pytest-cov>=3.0
black>=22.0
flake8>=4.0
mypy>=0.950

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
92% confidence
Finding

Leaving mypy unpinned permits future releases to be installed without review, creating avoidable supply-chain and reproducibility risk in development and CI environments. The risk is lower than for production dependencies, but deterministic builds are still a security best practice.

Content

Scanner excerpt · requirements.txt (reported line 12)May include surrounding context.

text
pytest-cov>=3.0
black>=22.0
flake8>=4.0
mypy>=0.950