Back to skill

Security audit

Foxtable 开发文档(进阶篇)

Security checks across malware telemetry and agentic risk

Overview

This is a Foxtable documentation skill with no executable payload, but it needs review because several examples teach high-impact workflows without adequate safety controls.

Install only if you want Foxtable reference documentation and can treat its code as legacy examples, not secure defaults. Before copying examples involving FTP, updates, SMS, fingerprints, ID cards, or approvals, add modern controls such as HTTPS/signatures, secret storage, authentication, authorization, audit logs, consent, encryption, retention limits, and manual review for sensitive actions.

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

Missing User Warnings

High
Confidence
98% confidence
Finding
The guide includes hard-coded FTP host, account, and password values in example code. Even if presented as sample values, embedding credentials in source encourages insecure patterns, risks accidental reuse in real deployments, and can expose live secrets if the values are not purely fictitious.

Missing User Warnings

High
Confidence
98% confidence
Finding
This sample again exposes fixed FTP credentials, this time in picture viewer configuration code. Repetition increases the chance developers copy the pattern verbatim, leading to credential leakage, unauthorized FTP access, and insecure secret distribution across client systems.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The document describes a remote auto-update mechanism that downloads archive files and automatically overwrites local application files, but it does not mention integrity verification, signature validation, transport security, rollback, or explicit user safety warnings. If the update path is compromised or intercepted, an attacker could deliver a malicious update and achieve arbitrary code execution on client systems.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The guide provides a fully silent update example that suppresses notifications and automatically installs updates without user awareness. In the context of an updater that replaces local files, silent execution increases the risk of unnoticed malicious or unintended changes and reduces the chance that users detect compromise or operational disruption.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The document shows an FTP update URL embedding a username and password directly in the address, which exposes credentials in plaintext configuration, logs, screenshots, browser history, and network traffic because FTP is not secure. An attacker who obtains these credentials could tamper with the update packages and distribute malicious code to all clients using the updater.

Missing User Warnings

Medium
Confidence
86% confidence
Finding
The skill recommends automatically ingesting inbound SMS into application tables and deleting messages from the SIM without warning about retention, audit, privacy, or verification controls. This can cause irreversible data loss, destroy forensic evidence, and process untrusted SMS content as business data with little operator visibility.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The SMS query examples automatically return inventory and pricing information based solely on incoming message format, without authentication, authorization, or rate limiting. An attacker who knows the number and query format could extract potentially sensitive business data by SMS.

Missing User Warnings

High
Confidence
96% confidence
Finding
The approval workflow allows incoming SMS content to approve or reject orders and even append remarks, but the example does not verify that the sender is an authorized approver. Because caller ID/SMS origin is not a trustworthy authentication factor, forged or misrouted messages could trigger unauthorized business actions.

Missing User Warnings

High
Confidence
95% confidence
Finding
The example generates web-accessible pages containing query results in response to SMS requests and returns a public URL, without discussing access control, expiration, or data classification. This can expose business data to anyone who obtains or guesses the link, and the SMS trigger itself is unauthenticated.

Missing User Warnings

High
Confidence
94% confidence
Finding
The fingerprint section instructs users to collect and store biometric templates but omits warnings about the sensitivity and permanence of biometric data. Compromise of stored fingerprint templates can create long-term privacy and identity risks because biometrics cannot be rotated like passwords.

Missing User Warnings

High
Confidence
93% confidence
Finding
The examples show automatic fingerprint-based login and approval actions on capture, but provide no warning about spoofing resistance, fallback handling, session binding, liveness detection, or false accept risk. Tying privileged actions directly to a biometric event can enable unauthorized access or approvals if the implementation or device is weak.

Missing User Warnings

High
Confidence
95% confidence
Finding
The identity-card reader example automatically reads and stores full identity data and photos, including national ID numbers and addresses, without warning about consent, legal restrictions, minimization, or secure storage. This creates substantial privacy, compliance, and identity theft risk if deployed as written.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.