ClawHub
Back to skill

Security audit

IPO监控

Security checks for vulnerabilities and agentic risk

Overview

This skill matches its stated IPO-monitoring purpose and shows no hidden, destructive, or deceptive behavior.

Before installing, confirm that sending IPO report content and operational alerts to your Feishu workspace is acceptable, keep webhook URLs secret, run in test mode first, and pin reviewed patched dependency versions if deploying this on a schedule.

SkillSpector

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

Unpinned Dependencies

Low
Category
Supply Chain
Content
# IPO监控技能 V2

# Python依赖
requests>=2.28.0
urllib3>=1.26.0
beautifulsoup4>=4.11.0
pyyaml>=6.0
Confidence
91% confidence
Finding
Using a lower-bound specifier like requests>=2.28.0 allows installation of many different versions depending on when and where the skill is deployed, which harms reproducibility and can unintentionally pull in vulnerable or breaking releases. In a security-sensitive automation skill, this increases supply-chain risk because the exact dependency set is not controlled.

Unpinned Dependencies

Low
Category
Supply Chain
Content
# Python依赖
requests>=2.28.0
urllib3>=1.26.0
beautifulsoup4>=4.11.0
pyyaml>=6.0
Confidence
91% confidence
Finding
The specifier urllib3>=1.26.0 does not guarantee a specific safe version and permits non-reproducible installs across environments. This weak dependency hygiene can expose deployments to newly introduced vulnerable releases or incompatibilities in HTTP handling code.

Unpinned Dependencies

Low
Category
Supply Chain
Content
# Python依赖
requests>=2.28.0
urllib3>=1.26.0
beautifulsoup4>=4.11.0
pyyaml>=6.0
Confidence
85% confidence
Finding
beautifulsoup4>=4.11.0 is unpinned, so builds are not deterministic and may consume future releases without review. While this package is lower risk than networking or deserialization libraries, unpinned dependencies still expand supply-chain and stability risk.

Unpinned Dependencies

Low
Category
Supply Chain
Content
requests>=2.28.0
urllib3>=1.26.0
beautifulsoup4>=4.11.0
pyyaml>=6.0
Confidence
94% confidence
Finding
pyyaml>=6.0 permits a range of versions and removes assurance that only a vetted release will be installed. Because YAML parsers have a history of unsafe deserialization issues, leaving this dependency unpinned is more dangerous in context than a typical parsing library.

Known Vulnerable Dependency: requests — 10 advisory(ies): CVE-2014-1830 (Exposure of Sensitive Information to an Unauthorized Actor in Requests); CVE-2024-47081 (Requests vulnerable to .netrc credentials leak via malicious URLs); CVE-2024-35195 (Requests `Session` object does not verify requests after making first request wi) +7 more

High
Category
Supply Chain
Confidence
88% confidence
Finding
The dependency entry allows requests versions with known advisories, and the finding indicates multiple historical vulnerabilities affecting this package family. In a skill likely to fetch external IPO data over the network, flaws in HTTP request handling, credential leakage, or certificate verification behavior can directly affect confidentiality and integrity.

Known Vulnerable Dependency: urllib3 — 10 advisory(ies): CVE-2025-66471 (urllib3 streaming API improperly handles highly compressed data); CVE-2024-37891 (urllib3's Proxy-Authorization request header isn't stripped during cross-origin ); CVE-2026-21441 (Decompression-bomb safeguards bypassed when following HTTP redirects (streaming ) +7 more

High
Category
Supply Chain
Confidence
90% confidence
Finding
urllib3 is a core HTTP transport library, and the requirement permits versions associated with several advisories, including proxy header leakage and decompression-related issues. For a monitoring skill that likely consumes remote web content, these weaknesses can increase exposure to SSRF-adjacent abuse, credential leakage, or denial of service from malicious responses.

Known Vulnerable Dependency: pyyaml — 8 advisory(ies): CVE-2019-20477 (Deserialization of Untrusted Data in PyYAML); CVE-2020-1747 (Improper Input Validation in PyYAML); CVE-2020-14343 (Improper Input Validation in PyYAML) +5 more

Critical
Category
Supply Chain
Confidence
96% confidence
Finding
PyYAML has a well-established history of unsafe deserialization vulnerabilities, and this requirement allows affected versions according to the advisory set. If any part of the skill loads YAML from untrusted or semi-trusted sources, exploitation could lead to arbitrary code execution or severe integrity compromise, making this especially dangerous despite the limited context in this file alone.

Static analysis

No suspicious patterns detected.