Cybercriminals Weaponize OpenClaw AI Agent in ClawHavoc Campaign to Distribute Infostealers
Cybercriminals have turned the OpenClaw AI agent into a convincing delivery mechanism for infostealers through a campaign called ClawHavoc.
Attackers uploaded hundreds of seemingly useful skills to the ClawHub catalog. These skills prompt users to install a mandatory tool or paste an encoded command into the terminal, all while appearing as legitimate configuration steps recommended by the AI assistant.
On macOS, victims are directed to commands that download the Atomic macOS Stealer (AMOS). On Windows, the same technique delivers password-protected archives and fake verification utilities, recreating the classic ClickFix social-engineering pattern but with an AI assistant acting as the trusted courier.
Researchers from Trellix discovered 341 malicious skills in total, 335 of which used fabricated installation requirements for AMOS. Repository history analysis revealed 1,184 suspicious packages associated with 12 distinct authors.
The stolen data includes passwords, browser credentials, cryptocurrency wallets, API keys, SSH keys, cloud accounts, .env files, source code, and tokens for connected services. Once OpenClaw has unrestricted terminal access, a simple text instruction can be converted into a PowerShell or Bash command.
Users are recommended to update OpenClaw, review all installed skills, remove anything suspicious, and rotate any potentially leaked credentials. Security experts advise running the agent in an isolated environment with minimal privileges and no access to production secrets.
Related articles
Server Log Analysis Reveals How Major AI Crawlers Actually Behave on Websites
A detailed examination of server access logs shows that AI vendors operate multiple distinct bots with separate purposes rather than a single crawler. GPTBot performs scheduled training data collection while OAI-SearchBot builds search indexes and ChatGPT-User fetches pages in direct response to user queries. The same pattern appears with PerplexityBot and Perplexity-User at Perplexity as well as ClaudeBot and user agents at Anthropic. Blocking all AI-related user agents in robots.txt therefore prevents both training crawls and live user-driven visits. Analysis of 515 million AI bot events found only 408 requests for llms.txt, confirming the file sees negligible adoption. Verification of IP addresses against vendor-published ranges remains the reliable method for distinguishing genuine bots from spoofed traffic. Effective practices focus on clean HTML structure, fast response times, and selective robots.txt rules that allow user-agent traffic while restricting training crawlers.
Nearly 70% of Companies Lack Control Over AI Agent Privileges, PAM Survey Finds
A recent survey conducted by AM Media among viewers and participants of the webinar 'How to Choose the Best PAM in 2026' shows that 68% of organizations fail to fully control privileges assigned to AI agents and automated services. Another 67% report insufficient oversight of API keys, tokens, and secrets, while 63% cite gaps in managing CI/CD and DevOps tool access. Traditional human administrator accounts are better protected at 34%, highlighting a shift in risk toward machine identities. Experts from NGR Softlab and Solar Group emphasize that service accounts often interact with multiple systems and require broad rights, making their compromise far more damaging than individual user breaches. JumpServer PAM CEO Denis Morozov noted that AI integration into PAM platforms could help map complex permission matrices and quantify risks for security teams. Participants also prioritized usability (72%) and ease of deployment (63%) when selecting PAM solutions over cost considerations.
Aligning AI Adoption Maturity with AI Security Using CMMI and Russian Regulatory Requirements
Organizations frequently operate at mismatched maturity levels between AI implementation and AI security controls, creating significant gaps that lead to incidents and regulatory violations. The analysis maps both dimensions onto the five-level CMMI scale, showing how adoption often outpaces protection and highlighting the risks of Shadow AI, uncontrolled agents, and non-compliance. Key frameworks including OWASP AIMA, Google SAIF, NIST AI RMF, and MITRE ATLAS are aligned to CMMI levels L1 through L5. Russian requirements under FSTEC Order No. 117, effective March 2026, introduce mandatory controls for trusted AI technologies, data handling, and statistical response validation that activate precisely at the L2-to-L3 transition. The article details predictable organizational states from denial to managed agentic systems and provides a practical matrix linking each CMMI level to minimum security requirements and specific Russian compliance anchors such as GOST R 56939-2024 and ISO/IEC 42001.
Study Finds Iterative AI Code Generation Accumulates Security Vulnerabilities Over Multiple Iterations
A 2025 IEEE-ISTAS 2025 research paper titled Security Degradation in Iterative AI Code Generation: A Systematic Analysis of the Paradox examined how repeated prompting of large language models leads to worsening code security. Researchers started with 10 secure code samples in C and Java, then applied four prompting strategies across 10 iterations each, generating 400 code samples that were analyzed with both manual review and automated scanners. The study found the strongest correlation between rising code complexity and vulnerability count, with 158 vulnerabilities emerging from feature-addition prompts and only 38 from explicit security-improvement requests. Even when asked to fix issues, GPT-4o frequently introduced new, subtler flaws such as timing side-channels, SQL injection risks, and use-after-free errors while addressing obvious problems. The authors recommend mandatory human review after every few iterations and greater use of SAST tools, noting that the illusion of progress can mask accumulating weaknesses. Limitations include testing only GPT-4o and the absence of human corrections during the iterative process.