Csharp Developer

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-style C#/.NET development skill with no executable installer or hidden access, though users should handle copied authentication examples carefully.

Safe to install as a C#/.NET coding reference skill. Review generated code before applying it to real services, especially authentication and database migration examples; keep JWT signing keys and connection strings in secure configuration such as environment variables, user-secrets, or a managed secrets store.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The trigger list includes several broad and common terms such as "C#", ".NET", and "Entity Framework", which can cause the skill to be selected in loosely related contexts rather than only when its specialized guidance is needed. This is not a code-execution flaw, but it can expand the skill's activation surface, increasing the chance of unintended invocation, prompt interference, or misrouting of tasks to a powerful implementation-oriented skill.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The example places a JWT signing secret directly in appsettings.json without warning that secrets should not be hardcoded or committed to source control. In practice, developers often copy documentation verbatim, which can lead to credential exposure, token forgery if the secret leaks, and weak secret management in production systems.

VirusTotal

61/61 vendors flagged this skill as clean.

View on VirusTotal