AgentReadyHomeAgent Listing

← Clean Paste - AI Text

Clean Paste - AI Text — agentic threat model

2.7AIVSS 2.7 · Low

Clean Paste is a low-risk, client-side utility with minimal agentic capabilities. Its privacy-first, browser-only architecture eliminates server-side data exposure risks, though it remains subject to standard web-based client-side vulnerabilities like XSS.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 4.3AARS uplift 0.15Factor sum 0.3/10Threat ×0.9Mitigation ×0.6
Autonomy of Action
0.00
Goal-Driven Planning
0.00
Self-Modification
0.00
Dynamic Tool Use
0.00
Persistent Memory
0.00
Contextual Awareness
0.10
Dynamic Identity
0.00
Multi-Agent Interactions
0.00
Non-Determinism
0.10
Opacity & Reflexivity
0.10

Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.

MAESTRO 7-layer threat model

Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.

L1 · Foundation Models⚠ not certain from listing

Not certain from the listing — The tool claims to detect and remove watermarks from models like ChatGPT and Claude, but it is unclear if it uses a local foundation model (e.g., via WebNN/ONNX) or purely heuristic/statistical rules. If a local model is used, it could be vulnerable to adversarial inputs designed to bypass detection.

L2 · Data Operations✓ mapped

All processing occurs client-side in the browser with no data sent to servers. There is no persistent vector database, RAG pipeline, or centralized training data, which minimizes data exfiltration and poisoning risks.

L3 · Agent Frameworks✓ mapped

The tool does not appear to use an agentic orchestration framework. It operates as a direct text-processing utility, meaning threats like tool misuse, recursive loop exploitation, or memory poisoning are not applicable.

L4 · Deployment & Infrastructure✓ mapped

Deployed as a static web application. Infrastructure risks are limited to CDN/hosting compromise (supply chain attacks modifying the frontend code) or client-side XSS, rather than server-side container escape or privilege escalation.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — Because processing is entirely local and privacy-first, there is likely no centralized logging or telemetry. This prevents data leaks but creates a blind spot for developers regarding bypass techniques or tool abuse.

L6 · Security & Compliance (cross-cutting)✓ mapped

The privacy-first design with zero server-side data retention inherently aligns with data minimization principles (GDPR/CCPA). There is no user authentication or access control, which is typical and acceptable for a public utility of this nature.

L7 · Agent Ecosystem✓ mapped

This tool does not interact with other agents or marketplaces, making ecosystem-level threats like cascading agent failures or agent-to-agent trust abuse non-existent.

MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).