registry / Remote code execution / devil-ai
devil-ai
Devil AI — AI-powered coding assistant. Install everything with: npm install -g devil-ai
This report shows the evidence for devil-ai@0.14.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.14.1, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package performs unconsented install-time remote shell execution and privileged host mutation. This is a concrete malicious install chain, not merely a user-invoked setup capability.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm postinstall during package installation
Impact
An install can modify the host and execute code supplied by remote installer endpoints without an explicit setup command.
Mechanism
Automatic remote shell execution and global dependency installation
Attack narrative
The postinstall lifecycle hook invokes `devil-ai setup` automatically. Setup checks for tools and, when absent, runs a NodeSource script through bash with sudo, runs the OpenCode installer through bash, and installs OmniRoute globally. This turns a normal npm install into unprompted remote code execution and host-level dependency changes.
AI rationale
The package performs unconsented install-time remote shell execution and privileged host mutation. This is a concrete malicious install chain, not merely a user-invoked setup capability.
Evidence
package.jsondist/cli.jsbin/devil-ai
Network endpoints2
deb.nodesource.com/setup_lts.xopencode.ai/install
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs the package setup command.
- Setup runs remote shell installers and privileged system package installation without user confirmation.
- Setup globally installs an additional package during npm installation.
Evidence against
- No source evidence of credential harvesting or unrelated data exfiltration.
- Telegram networking is part of the explicitly invoked bot runtime, not the install hook.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "const{execSync}=require('child_process');try{execSync('devil-ai setup',{stdio:'inherit'})}catch(e){console.log('\\n ⚡ Devil AI installed! Run \\x1b[1mdevil-ai setup\\x1b[...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "const{execSync}=require('child_process');try{execSync('devil-ai setup',{stdio:'inherit'})}catch(e){console.log('\\n ⚡ Devil AI installed! Run \\x1b[1mdevil-ai setup\\x1b[...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgdist/telegram.jsView file
1import { execSync, spawn } from "node:child_process";
L2: import { createServer } from "node:http";
High
Child Process
Package source references child process execution.
dist/telegram.jsFindings
1 Critical5 High3 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/telegram.js
HighShelldist/shell-env.js
HighSame File Env Network Executiondist/opencode.js
HighSandbox Evasion Gated Capabilitydist/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to devil-ai@0.14.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing devil-ai@0.14.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.