Crypto Arbitrage Monitor

• Outcome: Pass
• Latest audit: May 29, 2026 · 8:26 PM UTC
• Version: 1.0.0

Overview

This is a disclosed crypto price monitor that polls public exchange data and optionally sends user-configured alerts, with no evidence of trading, destructive behavior, hidden persistence, or data theft.

Install only if you are comfortable running Python packages from PyPI, preferably pin or lock dependency versions yourself, keep Feishu/Telegram credentials private, configure only alert destinations you control, and remember the monitor will keep polling exchange APIs until stopped.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (6)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 92% confidence
• Finding: The skill documentation describes network-capable behavior such as querying multiple exchanges and sending Feishu/Telegram alerts, but the skill metadata does not declare corresponding permissions. Missing permission declarations weaken transparency and policy enforcement, making it easier for a skill to perform outbound communication that users or a platform may not expect.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

ccxt>=4.0.0
requests>=2.28.0
python-dotenv>=1.0.0

• Confidence: 95% confidence
• Finding: The dependency is specified with a lower bound only (`ccxt>=4.0.0`), which allows future unreviewed versions to be installed. This weakens build reproducibility and can introduce breaking changes or newly introduced vulnerable releases into the skill without any code change.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

ccxt>=4.0.0
requests>=2.28.0
python-dotenv>=1.0.0

• Confidence: 98% confidence
• Finding: `requests>=2.28.0` is unpinned, so installations may resolve to different versions over time, including versions later found vulnerable or behaviorally incompatible. Because this skill monitors exchanges and may send outbound alerts, dependency drift in an HTTP client increases supply-chain and transport-security risk.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

ccxt>=4.0.0
requests>=2.28.0
python-dotenv>=1.0.0

• Confidence: 93% confidence
• Finding: `python-dotenv>=1.0.0` is also unpinned, permitting unreviewed future releases to be installed. While lower impact than a network-facing library, it still creates avoidable supply-chain risk and can pull in versions with security or compatibility issues.

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: 90% confidence
• Finding: The requirement references `requests` without an upper bound or a known patched pin, and the package has multiple published advisories affecting some versions, including credential leakage and TLS/request verification issues. In this skill's context, which likely performs network calls to exchanges and alerting endpoints, an affected `requests` version could expose secrets or enable unsafe outbound connections.

Known Vulnerable Dependency: python-dotenv — 1 advisory(ies): CVE-2026-28684 (python-dotenv: Symlink following in set_key allows arbitrary file overwrite via )

Low

• Category: Supply Chain
• Confidence: 82% confidence
• Finding: `python-dotenv` has a reported advisory related to symlink following in `set_key`, which can lead to arbitrary file overwrite in affected versions. If this skill ever writes `.env` data or manipulates environment files in a writable workspace, that could be abused to overwrite unintended files, though the practical risk depends on actual usage.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.