Security audit

Bambu Lab

Security checks across malware telemetry and agentic risk

Overview

The skill does what it says for Bambu printer control, but it ships with hardcoded printer credentials and weak TLS handling that users should review before installing.

Install only after replacing the bundled host, serial number, and access code with your own secure configuration. Treat the printer serial and access code as credentials, rotate them if the included values were ever real, and understand that commands can pause, stop, or otherwise affect an active physical print job.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (7)

Tp4

High

Category: MCP Tool Poisoning
Confidence: 74% confidence
Finding: The documented behavior exceeds the stated purpose, including additional printer control actions, raw MQTT visibility, notification integrations, and local state storage. This is dangerous because users may grant trust based on the high-level description while the skill performs broader actions that increase attack surface and operational risk.

Context-Inappropriate Capability

High

Confidence: 99% confidence
Finding: The documentation exposes a concrete printer serial number and access code directly in the skill file, which is credential disclosure. In the context of a printer-control skill, these secrets can allow unauthorized parties on the network to connect to the device, monitor it, or issue control commands such as pause or stop.

Missing User Warnings

High

Confidence: 98% confidence
Finding: The README publishes what appear to be real device credentials: a printer serial number used as MQTT username and an access code used as password. Even in a local-network context, exposing secrets in documentation normalizes credential leakage and may enable unauthorized control of the printer if the values are real, reused, or copied into deployments without rotation.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The skill documentation includes and instructs use of sensitive printer credentials without warning users that the access code is secret material. This increases the likelihood of accidental disclosure, reuse in unsafe contexts, and insecure copy-pasting into logs, chats, or version control.

Missing User Warnings

Medium

Confidence: 99% confidence
Finding: The script hardcodes the printer serial and access code, which exposes sensitive device credentials to anyone who can read the file, repository, logs, backups, or packaged skill contents. Because the same script also disables TLS certificate verification, an attacker on the local network has an easier path to use or intercept these credentials and send unauthorized printer commands.

Missing User Warnings

Medium

Confidence: 99% confidence
Finding: The script hardcodes the printer host, serial number, and especially the MQTT access code as default values, exposing sensitive credentials directly in source and process execution context. Anyone with access to the script, logs, backups, or environment can reuse those credentials to monitor or control the printer remotely on the LAN.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The script hardcodes and uses printer identifiers and an access credential to authenticate over MQTT, while also disabling TLS certificate verification elsewhere in the client setup. In this skill context, that combination is risky because it exposes sensitive local-device credentials in source code and weakens transport trust, increasing the chance of credential disclosure or unauthorized printer control on the LAN.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.