Back to skill

Security audit

STX Copilot

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent IBM Transformation Extender reference skill, but it includes unsafe operational examples that could expose sensitive financial data or create weak administrative access if copied into real systems.

Review this skill before installing in production-facing workflows. Treat its examples as reference material only: do not enable WTX_DUMP_DATA or TRACE logging on real payment/customer data without approval, redaction, restricted log access, and short retention, and do not copy the admin/secret Launcher user example into any environment.

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

T09 · Insecure Skill Coding Practices

Error
Location
references/execution.md:67
Finding

Predictable Administrative Credentials and Unsafe Shell Argument Handling

Content
View full analysis
Remediation
View remediation
;login:;pwd:' ``` - Prefer an interactive password prompt or an approved secret manager instead of placing passwords in command-line arguments. Command-line secrets may be exposed through shell history, process listings, terminal logs, or automation output. - Require a unique, randomly generated password that meets the organization's password policy. - Document immediate rotation if temporary bootstrap credentials must be used. - Restrict the Launcher administration listener to a dedicated management network or localhost where possible. - Apply firewall controls, authentication rate limiting, audit logging, and least-privilege administrative roles. - Add a warning that the example is illustrative and must never be copied unchanged into production. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
references/debugging.md:31
Finding

Financial Message Payloads Can Be Exposed Through Plaintext Diagnostic Logs

Content
View full analysis
Remediation
View remediation
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 (6)

Vague Triggers

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill explicitly says 'When in doubt, trigger,' which encourages unnecessary invocation beyond clear user intent. Over-broad activation increases the chance that unrelated user data or prompts are routed into a specialized finance/integration skill, causing context over-collection, privacy exposure, and confused or unsafe task execution.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The debugging guidance recommends enabling WTX_DUMP_DATA to capture input data in logs, but the warning is minimal and not actionable for sensitive financial/integration payloads. In this skill's context, inputs may include SWIFT, ISO 20022, COBOL, or other production message data containing regulated or confidential information, so logging raw payloads can create material data leakage risk.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The documentation instructs users to enable WTX_DUMP_DATA=true, which causes full input data to be written to logs. In an ITX/WTX context, inputs often contain financial, EDI, COBOL, or other sensitive business payloads, so this can expose regulated or confidential data to persistent log storage and any systems or personnel with log access.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The customer_overrides.properties example includes WTX_DUMP_DATA=true in a persistent logging configuration without a nearby privacy/security warning. Because this example is likely to be copied into real environments, it increases the risk of ongoing sensitive data leakage into application logs, especially in production B2B and financial transformation deployments.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The document says the Launcher activates execution based on events such as file arrival, MQ message, HTTP request, or schedule, but it does not define what specific events, endpoints, message patterns, or filters should trigger a run. In markdown documentation, this kind of broad invocation description can create ambiguity about when the skill should activate versus when it should not.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The documentation shows launcheradmin.sh -adduser user:admin;login:admin;pwd:secret, which normalizes embedding plaintext credentials directly in command lines. Command-line secrets can be exposed through shell history, process listings, logs, screenshots, and copied documentation, increasing the chance of credential disclosure and insecure reuse in real deployments.

Content

No source excerpt is available for this finding.