Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

clawsec-nanoclaw

v0.0.4

Use when checking for security vulnerabilities in NanoClaw skills, before installing new skills, or when asked about security advisories affecting the bot

0· 613·7 current·7 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for davida-ps/clawsec-nanoclaw.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "clawsec-nanoclaw" (davida-ps/clawsec-nanoclaw) from ClawHub.
Skill page: https://clawhub.ai/davida-ps/clawsec-nanoclaw
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install clawsec-nanoclaw

ClawHub CLI

Package manager switcher

npx clawhub@latest install clawsec-nanoclaw
Security Scan
Capability signals
CryptoRequires walletRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name, description and code/files align: the skill provides advisory feed fetching, signature verification, MCP tools and a host-side integrity monitor. The host imports and cache location are consistent with a security monitoring tool.
Instruction Scope
Runtime instructions direct the operator to copy files into NanoClaw, register MCP tools in the container, and add host IPC handlers and an AdvisoryCacheManager in host startup. These steps legitimately require host filesystem and process integration, but they also enable actions that read/modify host files (create baselines, auto-restore, quarantine), which are powerful and must be gated.
Install Mechanism
No registry install spec (instruction-only) but full source is included and INSTALL.md instructs manual copying into host/agent code. That is expected for a host-integrated skill but means code will run with host privileges when installed—verify files before copying.
Credentials
The skill requests no environment variables or secrets. It fetches a remote feed (https://clawsec.prompt.security) and uses a pinned public key embedded in code for signature verification, which is appropriate and reduces trust-on-first-use risk.
!
Persistence & Privilege
The skill requires modifying host startup code and writing to host-managed state (/workspace/project/data). The integrity monitor can auto-restore critical files and the MCP tools include an approve_change action; without strict host-side authorization this could let container agents or scheduled tasks approve or re-baseline tampered files, enabling persistence for malicious changes. always:false mitigates forced inclusion, but the required host integration grants significant privileges.
What to consider before installing
Before installing: 1) Review the host-side code (host-services/*, guardian/*) yourself—do not rely on the embedded README alone. 2) Confirm the pinned public key is correct and the feed domain (clawsec.prompt.security) is trusted. 3) When integrating IPC handlers, ensure the host-side handlers enforce caller authorization (which agent/group can call approve_change, clawsec_approve_change, or clawsec_check_integrity) and do not blindly accept container requests. 4) Treat baselines and the advisory cache as high-value assets: run them on the host with least privilege, store baselines where only the host process can write, and audit who can invoke 'approve' operations. 5) If you plan to enable auto-restore, require a manual approval workflow (or restrict approve_change) to prevent agents or malicious scheduled tasks from approving their own changes. 6) Consider installing in a staging environment first and run the provided tests. If you want more assurance, request a code review of the host IPC handlers to confirm access controls and logging are sufficient.

Like a lobster shell, security has layers — review code before you run it.

latestvk973yg38hv8xx6q1s4763d110s84yeem
613downloads
0stars
4versions
Updated 11h ago
v0.0.4
MIT-0

ClawSec for NanoClaw

Security advisory monitoring that protects your WhatsApp bot from known vulnerabilities in skills and dependencies.

Overview

ClawSec provides MCP tools that check installed skills against a curated feed of security advisories. It prevents installation of vulnerable skills, includes exploitability context for triage, and alerts you to issues in existing ones.

Core principle: Check before you install. Monitor what's running.

When to Use

Use ClawSec tools when:

  • Installing a new skill (check safety first)
  • User asks "are my skills secure?"
  • Investigating suspicious behavior
  • Regular security audits
  • After receiving security notifications

Do NOT use for:

  • Code review (use other tools)
  • Performance issues (different concern)
  • General debugging

MCP Tools Available

Pre-Installation Check

// Before installing any skill
const safety = await tools.clawsec_check_skill_safety({
  skillName: 'new-skill',
  skillVersion: '1.0.0'  // optional
});

if (!safety.safe) {
  // Show user the risks before proceeding
  console.warn(`Security issues: ${safety.advisories.map(a => a.id)}`);
}

Security Audit

// Check all installed skills (defaults to ~/.claude/skills in the container)
const result = await tools.clawsec_check_advisories({
  installRoot: '/home/node/.claude/skills'  // optional
});

if (result.matches.some((m) =>
  m.advisory.severity === 'critical' || m.advisory.exploitability_score === 'high'
)) {
  // Alert user immediately
  console.error('Urgent advisories found!');
}

Browse Advisories

// List advisories with filters
const advisories = await tools.clawsec_list_advisories({
  severity: 'high',               // optional
  exploitabilityScore: 'high'     // optional
});

Quick Reference

TaskToolKey Parameter
Pre-install checkclawsec_check_skill_safetyskillName
Audit all skillsclawsec_check_advisoriesinstallRoot (optional)
Browse feedclawsec_list_advisoriesseverity, type, exploitabilityScore (optional)
Verify package signatureclawsec_verify_skill_packagepackagePath
Refresh advisory cacheclawsec_refresh_cache(none)
Check file integrityclawsec_check_integritymode, autoRestore (optional)
Approve file changeclawsec_approve_changepath
View baseline statusclawsec_integrity_statuspath (optional)
Verify audit logclawsec_verify_audit(none)

Common Patterns

Pattern 1: Safe Skill Installation

// ALWAYS check before installing
const safety = await tools.clawsec_check_skill_safety({
  skillName: userRequestedSkill
});

if (safety.safe) {
  // Proceed with installation
  await installSkill(userRequestedSkill);
} else {
  // Show user the risks and get confirmation
  await showSecurityWarning(safety.advisories);
  if (await getUserConfirmation()) {
    await installSkill(userRequestedSkill);
  }
}

Pattern 2: Periodic Security Check

// Add to scheduled tasks
schedule_task({
  prompt: "Check advisories using clawsec_check_advisories and alert when critical or high-exploitability matches appear",
  schedule_type: "cron",
  schedule_value: "0 9 * * *"  // Daily at 9am
});

Pattern 3: User Security Query

User: "Are my skills secure?"

You: I'll check installed skills for known vulnerabilities.
[Use clawsec_check_advisories]

Response:
✅ No urgent issues found.
- 2 low-severity/low-exploitability advisories
- All skills up to date

Common Mistakes

❌ Installing without checking

// DON'T
await installSkill('untrusted-skill');
// DO
const safety = await tools.clawsec_check_skill_safety({
  skillName: 'untrusted-skill'
});
if (safety.safe) await installSkill('untrusted-skill');

❌ Ignoring exploitability context

// DON'T: Use severity only
if (advisory.severity === 'high') {
  notifyNow(advisory);
}
// DO: Use exploitability + severity
if (
  advisory.exploitability_score === 'high' ||
  advisory.severity === 'critical'
) {
  notifyNow(advisory);
}

❌ Skipping critical severity

// DON'T: Ignore high exploitability in medium severity advisories
if (advisory.severity === 'critical') alert();
// DO: Prioritize exploitability and severity together
if (advisory.exploitability_score === 'high' || advisory.severity === 'critical') {
  // Alert immediately
}

Implementation Details

Feed Source: https://clawsec.prompt.security/advisories/feed.json

Update Frequency: Every 6 hours (automatic)

Signature Verification: Ed25519 signed feeds Package Verification Policy: pinned key only, bounded package/signature paths

Cache Location: /workspace/project/data/clawsec-advisory-cache.json

See INSTALL.md for setup and docs/ for advanced usage.

Real-World Impact

  • Prevents installation of skills with known RCE vulnerabilities
  • Alerts to supply chain attacks in dependencies
  • Provides actionable remediation steps
  • Zero false positives (curated feed only)

Comments

Loading comments...