Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Scan binaries and scripts for malicious patterns before trusting them. Use when installing skills, evaluating unknown binaries, or auditing tool dependencies.
Scan binaries and scripts for malicious patterns before trusting them. Use when installing skills, evaluating unknown binaries, or auditing tool dependencies.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Lightweight malware detection for macOS and Linux binaries/scripts. Ported from the Harkonnen antimalware engine.
Binary Analysis: Mach-O (macOS) and ELF (Linux) parsing Suspicious dylibs/shared objects (Frida, injection frameworks) Missing/invalid code signatures (macOS) Disabled security features (PIE, NX, RELRO) Packed/encrypted binaries (high entropy) Pattern Detection: Shellcode byte sequences Suspicious API references (process injection, keylogging, etc.) Network indicators (embedded URLs, IPs) Encoded payloads (base64 blobs) Script Analysis: Dangerous shell patterns (curl|bash, eval, etc.) Obfuscation indicators Privilege escalation attempts
# Scan a single binary node bin/scan.js /path/to/binary # Scan a skill folder node bin/scan.js /path/to/skill-folder # JSON output for automation node bin/scan.js /path --json # Only show threats node bin/scan.js /path --quiet
0 - Clean (score โค 20) 1 - Suspicious (score 21-60) 2 - High threat (score > 60)
Each file receives a score from 0-100: ScoreLevelMeaning0-20CLEANNo significant findings21-40LOWMinor concerns, probably safe41-60MEDIUMSuspicious patterns, review manually61-80HIGHLikely malicious or dangerous81-100CRITICALKnown malicious patterns
Use before installing or trusting unknown binaries: // Example: scan before allowing a skill's binary const { scanFile } = require('openscan/lib/scanner'); async function checkBinary(binPath) { const result = await scanFile(binPath); if (result.threatScore > 40) { throw new Error(`Binary failed security scan: ${result.findings.join(', ')}`); } return true; }
Not a replacement for full antivirus Signature-based detection is minimal (no hash database) May produce false positives on legitimate security tools Cannot detect all obfuscation techniques
Detection logic ported from Harkonnen antimalware engine.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.