Back to skill

Security audit

OpenClaw Status API

Security checks for vulnerabilities and agentic risk

Overview

This package is not clearly malicious, but it advertises a paid live status API while the reviewed code does not enforce payment and returns hard-coded health data.

Review this carefully before installing or deploying. It is suitable only as a prototype unless payment verification, recipient configuration, real health checks, dependency pinning, and external-location-data disclosure are fixed.

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

T09 · Insecure Skill Coding Practices

Error
Location
index.js:26
Finding

Payment Enforcement Is Completely Bypassed

Content
View full analysis
{ ``` ```js app.get('/api/geocode', requirePayment, async (req, res) => { ``` ```js app.get('/api/weather', requirePayment, async (req, res) => { ``` ### Technical Analysis Both implementations read a possible payment header but never inspect or validate its value. They unconditionally invoke `next()`, including when neither payment header exists. Consequently, the application never calls its payment-required helper and never returns the advertised HTTP 402 response. A secure x402 implementation must validate the payment proof cryptographically and confirm the expected network, asset, amount, recipient, expiration, and replay status. Merely checking for a header would also be insufficient because an attacker could supply an arbitrary string. ### Attack Path 1. An attacker sends a request without an `x-payment` or `payment-signature` header: ```http GET /api/geocode?q=London HTTP/1.1 Host: target.example ``` 2. `requirePayment` reads two undefined header values. 3. The middleware unconditionally calls `next()`. 4. The endpoi ...[truncated 684 chars]
Remediation
View remediation

other

Warning
Location
index.js:34
Finding

Status and Health Results Are Fabricated from Static Constants

Content
View full analysis
{ res.json({ success: true, platform: 'OpenClaw Status API', timestamp: new Date().toISOString(), endpoints: ['/api/status', '/api/geocode', '/api/weather'], agents: [ { name: 'main', status: 'active' }, { name: 'ceo', status: 'active' }, { name: 'biz', status: 'active' }, { name: 'polymarket', status: 'active' }, ], cronJobs: [ { name: 'Simmer Trading', schedule: '15min', status: 'active' }, { name: 'CLAWMART Revenue', schedule: '12hr', status: 'active' }, { name: 'VIRTUALS Scanner', schedule: '1day', status: 'active' }, ] }) }) ``` The alternative route similarly constructs static data rather than retrieving status from authoritative sources: ```js async function handler(request) { // Get agent status from various sources const agents = [ { name: 'main', status: 'active', uptime: '24h' }, { name: 'ceo', status: 'active', uptime: '24h' }, { name: 'biz', status: 'active', uptime: '24h' }, { name: 'polymarket', status: 'active', uptime: '12h' }, { name: 'research', status: 'idle', uptime: '6h' }, ] const cronJobs = [ { name: 'Simmer Trading', schedule: '15min', status: 'active' }, { name: 'X402 Health', schedule: '1hr', status: 'active' }, { name: 'VIRTUALS Scanner', schedule: '1day', status: 'pending' }, { name: 'CLAWMART Revenue', schedule: '12hr', status: 'active' }, ] return NextResponse.json({ success: true, timestamp: new Date().toISOString(), agents, cronJobs, platform: 'OpenClaw', version: '1.0.0', }) ...[truncated 1536 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
index.js:7
Finding

Malformed and Inconsistent Payment Recipient Configuration

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
package.json:8
Finding

Dependency Resolution Is Not Reproducible

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

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
99% confidence
Finding

The payment middleware claims to enforce payment, but it unconditionally calls next() and never validates a payment header or returns the defined 402 response. This means all endpoints protected by requirePayment are effectively free and accessible, creating an authorization and business-logic bypass for any paywalled API functionality.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The geocoding endpoint forwards the user-provided q search query to the external Nominatim service via axios.get, which transmits user input off-system. Although there is an internal comment naming the provider, there is no user-facing warning, confirmation, or disclosure in code indicating that user-supplied location queries are sent to a third party.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The weather endpoint builds a request to the external Open-Meteo API using user-supplied latitude and longitude values, which can reveal user location information. The file contains only an internal comment about the provider and no user-facing disclosure or confirmation that location data is being sent externally.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The middleware and surrounding comments imply that API access is payment-gated, but the implementation unconditionally calls next() and never verifies the payment header. This creates an authorization bypass: clients can access endpoints intended to require payment without paying, undermining the service's access-control and monetization model.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The geocode endpoint forwards the user-provided q parameter to the Nominatim service via axios.get. While the code has an internal comment noting the service is used, there is no user-facing warning, confirmation, or disclosure that user input will be transmitted to a third-party API.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · index.js (reported line 100)May include surrounding context.

js
if (!lat || !lon) return res.status(400).json({ error: 'Missing lat/lon' })
  
  try {
    const response = await axios.get(`https://api.open-meteo.com/v1/forecast`, {
      params: {
        latitude: lat,
        longitude: lon,

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · server.js (reported line 81)May include surrounding context.

js
if (!lat || !lon) return res.status(400).json({ error: 'Missing lat/lon' })
  
  try {
    const response = await axios.get(`https://api.open-meteo.com/v1/forecast`, {
      params: {
        latitude: lat,
        longitude: lon,

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The weather endpoint transmits the request's lat and lon values to api.open-meteo.com. Although this is part of the implementation, the file contains no user-facing warning or documentation that location data is shared with an external service.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The dependency uses a caret range (^4.18.2), which allows npm to install newer minor and patch releases than were originally tested. This weakens build reproducibility and can unexpectedly introduce vulnerable or malicious upstream changes through the supply chain.

Content

Scanner excerpt · package.json (reported line 9)May include surrounding context.

json
"start": "node index.js"
  },
  "dependencies": {
    "express": "^4.18.2",
    "axios": "^1.6.0"
  }
}

Unverifiable Dependency: express has 5 known advisory(ies) (CVE-2024-10491 (Express ressource injection); CVE-2014-6393 (No Charset in Content-Type Header in express); CVE-2024-9266 (Express Open Redirect vulnerability) +2 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
78% confidence
Finding

Express has known advisories, and because the manifest does not pin the version, it is not possible to verify from this file alone which exact release will be installed. The immediate issue is uncertainty rather than confirmed exploitation, but that uncertainty is a real supply-chain risk because vulnerable versions may be pulled in during install.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The axios dependency is specified with a caret range (^1.6.0), so installs are not fully deterministic and may resolve to different versions over time. In a supply-chain context, this increases exposure to newly introduced vulnerable releases or compromised package updates.

Content

Scanner excerpt · package.json (reported line 10)May include surrounding context.

json
},
  "dependencies": {
    "express": "^4.18.2",
    "axios": "^1.6.0"
  }
}

Unverifiable Dependency: axios has 16 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
80% confidence
Finding

Axios has a substantial history of security advisories, and the unpinned version means the installed release cannot be verified from the manifest alone. Given axios is commonly used for outbound HTTP requests, unresolved version ambiguity can materially increase exposure to issues such as SSRF-related bypasses or request-handling flaws if a vulnerable release is resolved.

Content

No source excerpt is available for this finding.