Icd10 Cpt Coding Assistant

Security checks across malware telemetry and agentic risk

Overview

This is a local medical-coding helper with real privacy and accuracy caveats, but its behavior is disclosed and aligned with its purpose.

Install only for local, trusted use with de-identified notes or compliant PHI handling. Treat all recommendations as draft coding assistance, not authoritative billing advice, and verify codes, modifiers, payer rules, CMS guidance, and current AMA CPT materials with qualified coding or compliance staff before use.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (5)

Intent-Code Divergence

Low

Confidence: 78% confidence
Finding: The file claims a relatively safe posture, but the security checklist shows key controls such as path validation, output restriction, prompt-injection protections, sanitization, and sandboxing are not completed. This mismatch can create false assurance and lead operators to deploy the skill before basic safeguards for file handling and sensitive medical data are in place.

Vague Triggers

Medium

Confidence: 73% confidence
Finding: The activation description is broad enough to match many ordinary requests involving clinical notes or coding help, which can cause over-triggering. In a healthcare context, unintended invocation is more dangerous because the skill may process sensitive medical text and produce coding recommendations in situations where the user did not explicitly request automated coding assistance.

Natural-Language Policy Violations

Low

Confidence: 96% confidence
Finding: The document gives authoritative ICD-10-CM and CPT guidance that is specific to U.S. coding frameworks, but it does not clearly state that the guidance is U.S.-only, time/version dependent, or inappropriate for other jurisdictions. In a healthcare coding assistant, this can lead users to apply the wrong billing and diagnosis standards across regions or payer contexts, causing claim denials, compliance violations, and potentially harmful documentation or reimbursement decisions.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: This file provides detailed CPT coding guidance that could be used in billing and compliance workflows, but it does not place a prominent operational warning at the beginning that users must verify codes and rules against current official AMA/CMS and payer-specific sources before relying on them. In a medical coding assistant, stale or incomplete coding guidance can directly contribute to upcoding, undercoding, claim denials, reimbursement errors, or regulatory noncompliance, especially because some content appears outdated despite the closing note to verify the current year manual.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: This tool processes clinical notes, which commonly contain PHI/PII, and then prints derived results and excerpts to stdout without any explicit privacy warning, redaction, or safe-handling controls. In healthcare context, terminal output, logs, shell history, screen sharing, or redirected files can unintentionally expose sensitive patient information, making this more serious than in a non-medical skill.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal