Back to skill

Security audit

Concert Poster Generator

Security checks for vulnerabilities and agentic risk

Overview

This poster generator appears purpose-aligned, but it needs Review because it requires an API token, handles it unsafely on the command line, and sends it to an external service with uneven disclosure.

Review before installing. Use a dedicated, low-privilege Neta token, rotate it if it was ever pasted into shell history or logs, and prefer a version-pinned or trusted installer path. Be aware that prompts, reference IDs, and the token are sent to api.talesofai.com for image generation.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
concertpostergenerator.js:17
Finding

API Token Exposed Through Command-Line Arguments

Content
View full analysis

Vulnerability Details

File Location: concertpostergenerator.js:17-19, 36-43; SKILL.md:16-20, 25; README.md:24, 31, 37-38, 43, 65-77
Vulnerability Type: Sensitive credential exposure through process arguments
Risk Level: Medium

Vulnerable Code

javascript
if (a === '--size') {
  size = args[++i];
} else if (a === '--token') {
  tokenFlag = args[++i];
} else if (a === '--ref') {
  ref = args[++i];
}
javascript
async function main() {
  const { prompt, size, tokenFlag, ref } = parseArgs(process.argv);

  const TOKEN = tokenFlag;

  if (!TOKEN) {
    console.error('\n✗ Token required. Pass via: --token YOUR_TOKEN');
    console.error('  Get yours at: https://www.neta.art/open/');
    process.exit(1);
  }

The documentation consistently instructs users to put the secret in the command line:

bash
node concertpostergenerator.js "your prompt here" --token YOUR_TOKEN

Even the documented environment-variable example expands the secret into the child process argument vector:

bash
node concertpostergenerator.js "neon punk show poster" --token "$NETA_TOKEN"

Technical Analysis

The application obtains the Neta API token directly from process.argv. Command-line arguments are not an appropriate secret transport mechanism because they may be exposed through:

  • Process inspection facilities and monitoring software.
  • Shell command history.
  • CI/CD logs and task-runner diagnostics.
  • Terminal recording and support bundles.
  • Audit systems that record process invocation arguments.

Quoting an environment variable does not resolve the issue because the shell expands it before starting Node.js, placing the resulting token in the new process's argument vector.

The script subsequently sends this credential to the documented HTTPS API through the x-token header. That network use is expected for the skill's function; the vulnerability is the ...[truncated 1117 chars]

Remediation
View remediation

Remediation Suggestions

  1. Read the credential directly from an environment variable rather than from process.argv:

    javascript
    const TOKEN = process.env.NETA_TOKEN;
    
    if (!TOKEN) {
      console.error('NETA_TOKEN is required.');
      process.exit(1);
    }
    
  2. Alternatively, accept the token through a non-echoing interactive prompt or a protected credential manager.

  3. Remove or deprecate the --token option so users are not encouraged to expose secrets in process metadata.

  4. Update all examples to avoid literal credentials and command-line expansion:

    bash
    export NETA_TOKEN='token-value'
    node concertpostergenerator.js "your prompt here"
    
  5. Recommend that users disable history while setting sensitive environment variables or load them from a protected secret store.

  6. Ensure errors and diagnostics never include the token or complete request headers.

  7. Rotate any token known to have been used in logged command lines.

T08 · Insecure Dependencies

Warning
Location
SKILL.md:31
Finding

Unpinned Package Execution in Documented Installation Command

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:31-34; README.md:11-15
Vulnerability Type: Mutable third-party package execution without version or integrity verification
Risk Level: Medium

Vulnerable Code

SKILL.md contains the following installation instruction:

bash
npx skills add omactiengartelle/concert-poster-generator

README.md provides the same unpinned instruction:

bash
npx skills add omactiengartelle/concert-poster-generator

Technical Analysis

npx can resolve, download, and execute a package from the configured npm registry. The command does not specify an audited package version, integrity digest, lockfile, or trusted binary path. Consequently, the code executed by the installation command is mutable and may differ from the version evaluated during this audit.

This creates a supply-chain risk if:

  • The skills package or its maintainer account is compromised.
  • A malicious or defective future release is published.
  • Registry or package-resolution configuration redirects the package name to an unsafe source.
  • The user runs the command in an environment configured to use an untrusted registry.

No evidence was found that the currently audited project contains such a malicious dependency. The issue is that its documented installation procedure delegates code execution to an unpinned external package.

Attack Path

  1. An attacker compromises the package publisher, registry path, or package-resolution environment used for skills.
  2. The attacker publishes or serves a malicious package version under the expected package name.
  3. A user follows the documented npx skills add ... instruction.
  4. npx resolves the mutable package version and downloads it.
  5. Package entry-point or lifecycle code executes with the invoking user's permissions.
  6. The malicious package can access files, environment variables, network resources, and credentials avai ...[truncated 520 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin the installer to a specifically reviewed version:

    bash
    npx --yes skills@AUDITED_VERSION add omactiengartelle/concert-poster-generator
    
  2. Document the expected official registry and publisher identity.

  3. Publish and verify package integrity hashes or signatures where supported.

  4. Use a lockfile for repeatable installation in automated environments.

  5. Prefer a previously installed, organization-approved CLI rather than downloading and executing the current registry version on every installation.

  6. In CI/CD environments, install dependencies in a restricted container or sandbox with minimal filesystem, credential, and network access.

  7. Keep the pinned version current through an explicit review and upgrade process rather than relying on automatic resolution of the latest release.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (11)

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

The tool instructs users to obtain a token from Neta, then transmits that token in the x-token header to api.talesofai.com. Sending credentials obtained for one service to a different service is highly dangerous because it can expose user secrets to an unexpected party and indicates possible credential harvesting or abuse.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The README repeatedly instructs users to pass the API token via a --token command-line argument, which can expose secrets through shell history, process listings, audit logs, and terminal recordings. In this skill's context, that is more dangerous because the token is required to use a third-party API, so many users are likely to paste live credentials exactly as shown.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding

The skill declares only the Bash tool and omits any explicit permission or allowed-tools scope, even though its described usage requires outbound network access to the Neta API. That mismatch weakens least-privilege controls and can cause the skill to run with broader capabilities than users or platforms expect, increasing the chance of unintended external requests or abuse if the script is modified.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger guidance says to use the skill when someone asks to 'generate or create concert poster generator images,' which is vague and overly broad. Ambiguous invocation criteria can cause the agent to invoke this networked, token-using skill in situations where a simpler local response was intended, leading to unnecessary external API use, token exposure risk, or surprising actions.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The install command uses npx skills add omactiengartelle/concert-poster-generator without pinning a specific version, so consumers may fetch whatever package state is current at execution time. This creates a supply-chain risk: a later malicious or compromised release could be installed transparently and execute attacker-controlled code in the user's environment.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The API token is accepted via a command-line argument, which can expose it through shell history, process listings, audit logs, and other local telemetry. While this does not itself exfiltrate the secret remotely, it unnecessarily increases the chance of credential disclosure, especially on shared systems or developer workstations.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
70% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · concertpostergenerator.js (reported line 80)May include surrounding context.

js
let createRes;
  try {
    createRes = await fetch('https://api.talesofai.com/v3/make_image', {
      method: 'POST',
      headers,
      body: JSON.stringify(body),

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · concertpostergenerator.js (reported line 80)May include surrounding context.

js
let createRes;
  try {
    createRes = await fetch('https://api.talesofai.com/v3/make_image', {
      method: 'POST',
      headers,
      body: JSON.stringify(body),

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · concertpostergenerator.js (reported line 124)May include surrounding context.

js
let createRes;
  try {
    createRes = await fetch('https://api.talesofai.com/v3/make_image', {
      method: 'POST',
      headers,
      body: JSON.stringify(body),

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill claims to use the Neta AI API, but the implementation sends requests to TalesOfAI endpoints instead. This mismatch is dangerous because it can mislead users into trusting the tool with credentials and prompts that are actually transmitted to a different third-party service, which is a classic indicator of credential diversion or deceptive data exfiltration.

Content

No source excerpt is available for this finding.