new: OpenClaw AI agent family detection rules#6017
Open
0xdavidel wants to merge 1 commit into
Open
Conversation
new: Potential Autonomous AI Agent Activity Via Known Working Directory new: Potential Autonomous AI Agent Workspace File Creation new: Potential Autonomous AI Agent NPM Install new: Potential Autonomous AI Agent Postinstall Script Execution
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
Adds four detection rules covering the OpenClaw autonomous AI agent family and its copycat ecosystem (Nanobot, NanoClaw, Moltbot, Clawdbot, and several spiritual successors). All four projects share a common dot-folder workspace convention under the user profile (
~/.openclaw/,~/.nanobot/, etc.), which gives a stable detection surface across renames and forks.Rules and regression EVTXs were validated against a real install of
openclaw@2026.5.12(the current npm package) in a lab, includingopenclaw setup --non-interactive,openclaw skills list,openclaw skills install, andopenclaw config getinvocations. The real install bootstraps a documented agent state tree under~/.openclaw/with the following subfolders, all of which trigger the file-event rule:~/.openclaw/agents/<name>/sessions/(conversation sessions)~/.openclaw/memory/main.sqlite(agent persistent memory store)~/.openclaw/flows/registry.sqlite(gateway flow registry)~/.openclaw/identity/(identity store)~/.openclaw/plugin-skills/<skill>/(bundled skill plugins)~/.openclaw/plugins/(loaded plugins)~/.openclaw/workspace/(default agent workspace; configurable via--workspace)Coverage spans the install lifecycle:
npm installof any package in the family.node_modules.openclaw skills listoropenclaw config getfrom inside the workspace.Each rule ships with a positive
evtxregression test (one event,match_count: 1) plus the matching event extracted as JSON.Changelog
new: Potential Autonomous AI Agent Activity Via Known Working Directory
new: Potential Autonomous AI Agent Workspace File Creation
new: Potential Autonomous AI Agent NPM Install
new: Potential Autonomous AI Agent Postinstall Script Execution
Example Log Event
Sysmon EventID 1 fired when the operator installs the OpenClaw CLI from the public npm registry. Captured by the NPM install rule:
Sysmon EventID 11 fired during
openclaw setup --non-interactivewhen the agent created its persistent memory store. Captured by the workspace file creation rule:Equivalent paths and commands fire for
.nanobot\,.nanoclaw\,.clawdbot\,.moltbot\etc. Full JSON of both events is included in the regression_data tree.Fixed Issues
N/A
SigmaHQ Rule Creation Conventions