ninebot-device-skill

Security checks across malware telemetry and agentic risk

Overview

This skill clearly queries Ninebot vehicle status and location using a user-provided API key, but users should treat the key and location results as sensitive.

Install only if you trust this skill with your Ninebot Device Service key and vehicle telemetry. Prefer the NINEBOT_DEVICESERVICE_KEY environment variable over saving config.json, keep any config file private and out of source control, verify configured endpoints still point to the intended Ninebot service, and use location queries only for vehicles you own or are authorized to access.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The skill handles precise vehicle location and status data, which is sensitive physical-tracking information, but provides no user-facing privacy notice, consent language, retention statement, or warning about who can access the data. This increases the risk of users exposing location data without understanding the sensitivity or downstream handling implications.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The instructions encourage storing an API key in a local config file without warning that it is a secret credential or advising secure storage practices. This can lead to accidental disclosure through plaintext files, backups, source control commits, shared directories, or improper file permissions, enabling unauthorized access to vehicle data.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The spec instructs use of an API key from an environment variable or config file and communicates with a remote Ninebot endpoint, but it provides no warning about credential sensitivity, storage risks, or the fact that vehicle telemetry will be transmitted off-box. In this skill context, the missing guidance matters because the data includes device identifiers and potentially sensitive status/location information, increasing the chance of accidental secret exposure or uninformed use.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The spec documents retrieval of precise vehicle location information but does not warn users that this is highly sensitive personal data that can reveal a person's movements, home/work areas, or current whereabouts. In a vehicle-query skill, location access is expected functionality, but the absence of any privacy notice, consent guidance, or data-handling limits makes misuse or over-collection more dangerous.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal