Is "@speedscale/proxymock" on MCP Registry Safe to Install?

GitLab CI/CD · mcp · v2.5.369

A free desktop CLI that automatically creates mocks and tests from watching your app run.

Risk Assessment

Analyzed
80.34
out of 100
HIGH

37 security findings detected across all analyzers

MCP server analyzed for tool poisoning, prompt injection, and data exfiltration

Severity Breakdown

0
Critical
18
High
12
Medium
0
Low
0
Info

Finding Categories

18
Malware Signatures
12
IoC Indicators

YARA Rules Matched

9 rules(18 hits)
postinstall environment access credential env files UsingCommandLineArguments UsingShellInterpreterWhenExecutingOSCommands postinstall system command postinstall file manipulation postinstall file download postinstall crypto operations postinstall network communication

MCP Server Analysis

MCP servers expose tools and resources to AI assistants. Unlike browser extensions, they run as standalone processes with direct system access. Tool definitions are analyzed for prompt injection, data exfiltration, and tool poisoning patterns.

About This Extension

A free desktop CLI that automatically creates mocks and tests from watching your app run.

Detailed Findings

25 total

YARA Rule Matches

9 rules

Indicators of Compromise

Network indicators, suspicious strings, and potential IoCs extracted during analysis

URLs
5
Domains
6
Strings
12

All Indicators · 12

Domain
detected Domain: docs.speedscale.com

XIOC detected Domain: docs.speedscale.com

extracted_from_files

URL
detected URL: https://slack.speedscale.com/).

XIOC detected URL: https://slack.speedscale.com/).

extracted_from_files

URL
detected URL: https://downloads.speedscale.com/proxymock/$

XIOC detected URL: https://downloads.speedscale.com/proxymock/$

extracted_from_files

URL
detected URL: https://proxymock.io/

XIOC detected URL: https://proxymock.io/

extracted_from_files

URL
detected URL: https://slack.speedscale.com/

XIOC detected URL: https://slack.speedscale.com/

extracted_from_files

Domain
detected Domain: slack.speedscale.com

XIOC detected Domain: slack.speedscale.com

extracted_from_files

Domain
detected Domain: downloads.speedscale.com

XIOC detected Domain: downloads.speedscale.com

extracted_from_files

Domain
detected Domain: logger.info

XIOC detected Domain: logger.info

extracted_from_files

Domain
detected Domain: proxymock.io

XIOC detected Domain: proxymock.io

extracted_from_files

Domain
detected Domain: speedscale.com

XIOC detected Domain: speedscale.com

extracted_from_files

Other
detected Email: [email protected]

XIOC detected Email: [email protected]

extracted_from_files

URL
detected URL: https://docs.speedscale.com/proxymock/getting-started/quickstart-cli/).

XIOC detected URL: https://docs.speedscale.com/proxymock/getting-started/quickstart-cli/).

extracted_from_files

Security Analysis Summary

Security Analysis Overview

@speedscale/proxymock is a mcp extension published by GitLab CI/CD. Version 2.5.369 has been analyzed by the Risky Plugins security platform, receiving a risk score of 80.34/100 (HIGH risk) based on 37 security findings.

Risk Assessment

This extension presents critical security risk. Severe issues were detected, potentially including malware indicators, exposed secrets, or dangerous behaviors. Installation is strongly discouraged until these issues are addressed.

Findings Breakdown

  • High: 18 finding(s)
  • Medium: 12 finding(s)

What Was Analyzed

The security assessment covers multiple analysis categories:

  • Malware Detection: YARA rule matching against 2,400+ malware signatures
  • Secret Detection: Scanning for exposed API keys, tokens, and credentials
  • Static Analysis: Code-level security analysis for common vulnerability patterns
  • Network Analysis: Detection of suspicious network communications and endpoints
  • Obfuscation Detection: Identification of code obfuscation techniques

Developer Information

@speedscale/proxymock is published by GitLab CI/CD on the mcp marketplace.

Recommendation

This extension is not recommended for installation without thorough manual review. Consider alternatives with lower risk scores, or contact the developer to address the identified security concerns.

Frequently Asked Questions