Security audit

sportsinc-sportslink

Security checks for vulnerabilities and agentic risk

Overview

This looks like a real Sports Inc invoice adapter, but it needs review because it handles portal credentials, persists login sessions, masks browser automation, and can mark invoice documents consumed.

Install only for a controlled Sports Inc payables environment. Use least-privilege dealer credentials, keep SPORTSINC_WEB_STATE_PATH in a protected secret location if used at all, rotate/delete saved sessions, enable SPORTSINC_DRY_RUN while testing, and confirm the portal owner permits this browser automation.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 93% confidence
Finding: The skill performs sensitive operations—network access, shell execution, environment-variable handling, and file reads/writes—but declares no explicit permissions boundary. That creates a governance gap: callers and platform controls may not have a clear least-privilege contract for what the skill can access, increasing the blast radius if the helper script is misused, compromised, or invoked in an unexpected context.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The document explicitly recommends persisting authenticated Playwright storage state and describes it as an 'escape hatch' for MFA, which creates a reusable bearer-like session artifact on disk. If that file is read, copied, or mishandled, an attacker may gain portal access without needing fresh credentials or MFA, especially because the notes do not pair this guidance with storage protection, rotation, or deletion requirements.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The notes instruct operators to place portal credentials in environment variables but provide no caution about secret handling, exposure in shell history, CI logs, process inspection, or accidental leakage via screenshots/debug output. In an automation skill that also captures diagnostics and runs browser flows, weak secret-handling guidance materially increases the chance of credential compromise.

Ssd 3

Medium

Confidence: 97% confidence
Finding: The text does more than mention session reuse; it frames persisted authenticated state as a way around mandatory MFA/device verification. That normalizes retaining a post-auth session token specifically to bypass an additional authentication control, which weakens account protection and increases the blast radius of session-file theft.

Ssd 4

Medium

Confidence: 98% confidence
Finding: These notes document deliberate anti-detection measures for headless automation, including masking navigator.webdriver, changing the user agent, and using AutomationControlled-disabling flags. That is behavior intended to evade portal bot-detection and can violate site controls, reduce visibility for defenders, and enable scaled unauthorized automation if reused elsewhere.

Static analysis

No suspicious patterns detected.