Back to skill

Security audit

Dgx Spark Temperature

Security checks for vulnerabilities and agentic risk

Overview

This skill is narrowly meant to read DGX Spark temperatures, but it publishes and uses a plaintext SNMP community string for a specific internal host.

Install only if you own or are authorized to monitor the named DGX Spark host. Before publishing or using broadly, move the SNMP community string to protected configuration, prefer SNMPv3, rotate the exposed community, narrow the trigger wording to explicit DGX Spark requests, and avoid distributing internal host and system details.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
check_temperature.sh:7
Finding

Hardcoded SNMP Community String Transmitted over SNMPv2c

Content
View full analysis

Vulnerability Details

File Location: check_temperature.sh:7-14 (also documented in SKILL.md:13-17 and SKILL.md:52-57)
Vulnerability Type: Hardcoded credential and plaintext network protocol
Risk Level: Medium

bash
# SNMP target: dgx-spark1.fiber.house, v2c, community "licpub"
# MIB: LM-SENSORS (UCD-SNMP-MIB) OID 1.3.6.1.4.1.2021.13.16.2.1

SNMPDST="dgx-spark1.fiber.house"
COMMUNITY="licpub"
OID_BASE="1.3.6.1.4.1.2021.13.16.2.1"

# Fetch all name/value columns
WALK=$(snmpwalk -v2c -c "$COMMUNITY" "$SNMPDST" "$OID_BASE" 2>/dev/null)

Technical Analysis

The script embeds the SNMP community string licpub directly in source code and uses it with SNMPv2c. SNMPv2c does not provide encryption, message confidentiality, or cryptographically secure peer authentication. Consequently, the community string can be recovered by anyone who can read the repository or observe relevant network traffic.

The credential, target hostname, OID, and additional internal infrastructure details are also explicitly disclosed in SKILL.md. Although the community is described as read-only, it remains a reusable access credential and should not be committed to a distributable Skill package.

Exploitation requires either access to the repository or a network position capable of observing SNMP traffic, plus network reachability to the configured SNMP service. No command-injection or arbitrary-code-execution path was identified.

Attack Path

  1. An attacker obtains the Skill package or otherwise reads its source code.
  2. The attacker extracts the target dgx-spark1.fiber.house and community string licpub.
  3. If the attacker can reach the target's SNMP service, they issue SNMPv2c queries using the exposed community string.
  4. Alternatively, an attacker monitoring the relevant network captures the unencrypted SNMPv2c community string and replays it.
  5. The attacker enumerates information exposed by the commun ...[truncated 802 chars]
Remediation
View remediation

Remediation Suggestions

  1. Migrate to SNMPv3 with authentication and privacy, using strong authentication and encryption algorithms supported by the environment.
  2. Remove the community string from source code and documentation. Obtain any required credential from a protected secret manager, credential file with restrictive permissions, or an environment variable supplied at runtime.
  3. Rotate the exposed licpub community string after removing it from the repository and its history.
  4. Restrict SNMP access with host firewall rules, network ACLs, management-network segmentation, and source-address allowlisting.
  5. Limit the SNMP identity to the smallest necessary OID view, such as only the required LM-SENSORS subtree.
  6. Remove unnecessary internal hostname, physical location, operating-system, kernel, and architecture details from distributable documentation.
  7. Avoid exposing credentials in process arguments where feasible, because command-line arguments may be visible to other local users. Use a protected SNMP configuration mechanism supported by the deployed tooling.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger conditions are broad enough to match ordinary phrases like 'body temperature' or 'how hot things are running,' which can cause the skill to run in contexts unrelated to the DGX Spark. Because the skill performs a real network query to a specific host, accidental invocation can disclose internal infrastructure details and initiate unintended network activity.

Content

No source excerpt is available for this finding.

YARA rule 'network_reconnaissance': Network reconnaissance and scanning patterns [hacktools]

Medium
Category
YARA Match
Confidence
84% confidence
Finding

The documented use of snmpwalk with SNMPv2c and a plaintext community string against a specific host is a real reconnaissance-capable network action, even if intended for temperature monitoring. In this skill context it is less indicative of malware, but it still exposes internal hostnames, service usage, and credentials material that could be reused or encourage unauthorized querying.

Content

Scanner excerpt · SKILL.md (reported line 18)May include surrounding context.

dgx-spark-temperature

Read hardware temperature sensors on the DGX Spark via SNMP.

When to use

  • User asks for body temperature, DGX Spark temp, hardware temps, how hot things are running
  • Any temperature/hardware health check request for the DGX Spark

How to use

Run exec with:

text
bash <workspace>/skills/dgx-spark-temperature/check_temperature.sh

The script uses:

  • snmpwalk -v2c -c licpub dgx-spark1.fiber.house 1.3.6.1.4.1.2021.13.16.2.1
  • Parses LM-SENSORS MIB table: lmTempSensorsIndex, lmTempSensorsDevice, lmTempSensorsValue
  • Values are in milliCelsius — divide by 1000 for °C

Sensor mapping (16 sensors)

IDXSensor NameNotes
1asicGPU/GB10 ASIC
2Module0GPU Module 0
3mlx5-pci-0100:asicMellanox NIC #1 ASIC
4m

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The script embeds an SNMPv2c community string directly in source and uses it in a network query. SNMPv2c community strings act like cleartext shared secrets and are commonly exposed through source control, logs, or process inspection; they are also transmitted without modern cryptographic protection, making unauthorized monitoring or further device access easier if reused elsewhere.

Content

No source excerpt is available for this finding.

YARA rule 'network_reconnaissance': Network reconnaissance and scanning patterns [hacktools]

Medium
Category
YARA Match
Confidence
65% confidence
Finding

YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).

Content

Scanner excerpt · check_temperature.sh (reported line 14)May include surrounding context.

sh
eck_temperature — read DGX Spark temps via SNMP and format nicely
# Usage: bash check_temperature.sh
#
# Requires: snmpwalk (net-snmp-utils)
# SNMP target: dgx-spark1.fiber.house, v2c, community "licpub"
# MIB: LM-SENSORS (UCD-SNMP-MIB) OID 1.3.6.1.4.1.2021.13.16.2.1

SNMPDST="dgx-spark1.fiber.house"
COMMUNITY="licpub"
OID_BASE="1.3.6.1.4.1.2021.13.16.2.1"

# Fetch all name/value columns
WALK=$(snmpwalk -v2c -c "$COMMUNITY" "$SNMPDST" "$OID_BASE" 2>/dev/null)
if [ $? -ne 0 ] || [ -z "$WALK" ]; then
  echo "ERROR: SNMP walk failed"
  exit 1
fi

# Parse SNMP output using gawk
# OID format: iso.3.6.1.4.1.2021.13.16.2.1.COL.INDEX
# COL 1 = index (lmTempSensorsIndex), 2 = name (lmTempSensorsDevice), 3 = value (lmTempSensorsValue)
echo "$WALK" | gawk '
BEGIN {
  count = 0
}
{
  # Split the OID (first field) by dots to get column type and index
  split($1, oid_parts, ".")
  n = length(oid_parts)
  idx = oid_parts[n] + 0
  col = oid_parts[n-1] + 0

  if (col == 1 && idx > 0) {
    # lmTempSe

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill omits a clear warning that execution will perform an unauthenticated SNMPv2c query using a community string against an internal host. This reduces operator awareness and can lead to unintentional network access or exposure of environment-specific details without informed user consent.

Content

No source excerpt is available for this finding.