Back to skill

Security audit

OpenNexum

Security checks for vulnerabilities and agentic risk

Overview

OpenNexum is a coherent orchestration skill, but it handles credentials, generated shell commands, remote build tools, and background services in ways users should review carefully before installing.

Install only if you trust the repositories whose nexum contracts and config files will be processed. Before use, avoid custom webhook gatewayUrl values unless the token is scoped to that endpoint, review generated git commands before agents run them, and do not enable nexum watch/install unless you want a persistent user-level background service.

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 (3)

T09 · Insecure Skill Coding Practices

Error
Location
packages/cli/src/lib/webhook.ts:10
Finding

OpenClaw Hook Credential Disclosure to a Project-Controlled Webhook Endpoint

Content
View full analysis
): Promise { const envToken = process.env.OPENCLAW_HOOKS_TOKEN?.trim(); if (envToken) { return envToken; } const configToken = config.webhook?.token?.trim(); if (configToken) { return configToken; } return readOpenClawHooksToken(); } export function resolveWebhookAgentEndpoint( config: Pick ): string { return new URL( WEBHOOK_AGENT_PATH, withTrailingSlash(config.webhook?.gatewayUrl?.trim() || DEFAULT_WEBHOOK_GATEWAY_URL) ).toString(); } export async function postWebhookMessage(options: { projectDir: string; message: string; sessionName?: string; source: "callback" | "health" | "watch"; }): Promise { try { const config = await loadConfig(options.projectDir).catch( () => ({ webhook: undefined } as NexumConfig) ); const token = await resolveWebhookToken(config); if (!token) { console.warn(`[${options.source}] webhook skipped for ${options.projectDir}: no hooks token configured`); return false; } const endpoint = resolveWebhookAgentEndpoint(config); const response = await fetch(endpoint, { method: "POST", headers: { Authorization: `Bearer ${token}`, "Content-Type": "application/json" }, body: JSON.stringify({ message: options.message, name: "OpenNexum", agentId: config.webhook?.agentId?.trim() || "orchestrator", deliver: false, ...(options.sessionName ? { sessionName: options.sessionName } : {}) }) }); // ... } } async function readOpenClawHooksToken(): Promise { const ope ...[truncated 2832 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
packages/cli/src/commands/spawn.ts:107
Finding

Agent-Mediated Shell Command Injection Through Contract and Git Configuration

Content
View full analysis
quoteShellArg(file)).join(' '); const gitCommitCmd = gitRemote ? [ `git add -- ${quotedScopeFiles}`, `git commit -m "${commitMsg}"`, `git push -u ${gitRemote} ${gitBranch}`, ].join(' && ') : [ `git add -- ${quotedScopeFiles}`, `git commit -m "${commitMsg}"`, ].join(' && '); const promptContent = renderGeneratorPrompt({ contract: resolvedContract, task: { id: task.id, name: task.name }, gitCommitCmd, evalResultPath, fieldReportPath, lessons: [], projectDir, }); ``` The retry path in `packages/cli/src/commands/complete.ts` contains the same unsafe pattern: ```ts const quotedScopeFiles = contract.scope.files.map((file) => quoteShellArg(file)).join(' '); const gitCommitCmd = [ `git add -- ${quotedScopeFiles}`, `git commit -m "feat(${taskId.toLowerCase()}): implement ${contract.name} (iter ${nextIteration})"`, ].join(' && '); ``` The generated prompt directs the Agent to run the command unchanged: ```md ## Commit & Callback Instructions 完成实现后,依次执行以下命令: ```bash # 1. commit + push(命令已预生成为英文,直接运行,不要修改 commi ...[truncated 3530 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
package.json:6
Finding

Unpinned Remote Package Execution in Build and Test Scripts

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (110)

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
86% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
93% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

If the primary behavior is CLI selection and stub session record creation, then the description materially overstates actual orchestration functionality. This is chiefly dangerous because users may grant broader permissions or trust than the implementation warrants.

Content

No source excerpt is available for this finding.

Static analysis

Detected: suspicious.dynamic_code_execution, suspicious.env_credential_access

Dynamic code execution detected.

Critical
Code
suspicious.dynamic_code_execution
Location
packages/spawn/src/status.ts:19

Environment variable access combined with network send.

Critical
Code
suspicious.env_credential_access
Location
packages/cli/src/lib/webhook.ts:13