Security audit

huawei-cloud-msot-msopprof-operator-profiler

Security checks across malware telemetry and agentic risk

Overview

This profiling skill mostly matches its stated purpose, but it includes unsafe troubleshooting commands that can weaken host security or expose output files on shared systems.

Install only if you need Ascend operator profiling guidance. Before running its suggested commands, avoid disabling SELinux except as a last-resort diagnostic step, do not use chmod 777 for profiling directories, store profiling outputs in a private approved location, and review cleanup commands before executing them.

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 (5)

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The trigger list contains generic terms such as "profiler", "Ascend", "NPU", and "profile data", which can cause the skill to activate for requests that are only loosely related to this specific operator-profiling workflow. Unintended invocation can lead the agent to expose profiling-oriented guidance or run tooling in the wrong context, increasing the chance of unnecessary data collection or misuse of allowed tools.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The skill states that profiling data is exported to a profiling database and written to an output path, but it does not clearly warn users that execution may persist potentially sensitive performance artifacts on disk or in external storage. In a profiling context, these artifacts can reveal model structure, operator behavior, paths, and environment details, so lack of disclosure raises data handling and privacy risks.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The troubleshooting guidance tells users to run `setenforce 0` to disable SELinux enforcement, even if marked temporary, without warning about the security consequences or safer alternatives. Disabling SELinux weakens host protections and can expose the system to broader compromise if untrusted binaries, profiling tools, or workloads are executed afterward.

Missing User Warnings

Medium

Confidence: 98% confidence
Finding: The guidance recommends `chmod 777 /tmp/profiling`, making the output directory world-writable without any warning or constraint. On multi-user systems this enables tampering, symlink/race attacks, or unauthorized modification of profiler outputs and adjacent file operations, especially because `/tmp` is shared and commonly targeted.

Missing User Warnings

Medium

Confidence: 92% confidence
Finding: The verification script includes `rm -rf output_npu` without any warning, confirmation, or safety guard. While the target is a relative path rather than an obviously dangerous system location, it can still silently delete prior profiling results or unintended data if the working directory or path assumptions are wrong.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Static analysis

No suspicious patterns detected.