ASR AI Security Radar
Methodology Recent Incidents Get Notified

Back to incidents

AI security incident: OpenClaw has a command injection in maintainer clawtributors updater (GHSA-m7x8-2w3w-...

Incident date: February 18, 2026 | Published: February 25, 2026 | Source: GitHub Security Advisory | Classification confidence: 45%

This incident is part of the public archive and includes explicit AI-related signals from the cited source material. Review methodology.

Summary Command injection in the maintainer/dev script scripts/update-clawtributors.ts . ### Impact Affects contributors/maintainers (or CI) who run bun scripts/update-clawtributors.ts in a source checkout that contains a malicious commit author email (e.g. crafted @users.noreply.github.com values). Normal CLI usage is not affected ( npm i -g openclaw ): this script is not part of the shipped CLI and is not executed during routine operation. ### Affected Versions - Source checkouts: tags v2026.1.8 through v2026.2.13 (inclusive) - Version range (structured): >= 2026.1.8, < 2026.2.14 ### Details The script derived a GitHub login from git log author metadata and interpolated it into a shell command (via execSync ).

Why This Is AI-Related

This page is treated as AI-specific because the source material references copilot, which places the issue inside an AI workflow, model, assistant, or supporting dependency rather than a generic software bulletin.

  • copilot

Affected Workflow

Review AI plugins, copilots, model-serving helpers, CLI tools, and automation runtimes that execute system commands.

Likely Attack Path

An attacker can turn the vulnerable AI-adjacent component into a path for command execution on the host or service runtime.

Impact

The issue can create a path to command execution inside an AI-facing product, plugin, copilot, or supporting service runtime. Severity HIGH. Classification confidence 45%. Source channel GHSA.

Detection And Triage Signals

  • New shell or process activity from AI-facing services
  • Unexpected outbound connections or file writes after prompt or API activity
  • Privilege changes, container escapes, or suspicious job execution logs

Recommended Response

  • Identify every environment that runs the affected AI plugin, assistant, CLI, or supporting package.
  • Patch or isolate the vulnerable component and remove risky execution permissions while validation is in progress.
  • Review process execution, outbound connections, and file-write logs for signs of post-exploitation activity.

Compliance And Business Impact

Code execution paths create immediate risk of host compromise, credential theft, and downstream lateral movement.

Sources

Want alerts like this in real time?

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents