@addai/entity-runtime
Affected
- Versions:
0.2.45,0.2.46,0.2.47,0.2.48,0.2.49,0.2.50,0.2.51,0.2.52,0.2.53,0.2.55,0.2.56,0.2.58
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @addai/entity-runtime (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (248d92bb0f9ac7a066bb69c3f3ecea88241e5dd35ea1b61393896c88c07b0856)
The package runs a daemon that polls a hardcoded Supabase project (syhzpqqvrplaqdipcymw.supabase.co) via the RPC runtime_pick_next_request for remote-supplied job rows and spawns Claude Code / Codex / Kimi / Gemini / Grok in a PTY on the installer's host, driven by fields controlled by the paired remote party (prompt, permissionMode, appendSystemPrompt, allowedTools, model, workingDirectory). In dist/session-runner.js, spawnClaudeForRuntime invokes the agent binary through a login shell (['-l','-c','exec "$@"',...]) and, when input.permissionMode === 'bypassPermissions', passes --dangerously-skip-permissions, letting the remotely-driven AI agent execute arbitrary shell tools as the local user without any interactive prompt. On start, ensureBypassPermissionsAccepted() in dist/index.js also writes skipDangerousModePermissionPrompt: true into the installer's user-global ~/.claude/settings.json, disabling Claude Code's own bypass-permissions safety dialog for every future interactive Claude Code session the installer runs — not just those spawned by this daemon. dist/capabilities.js additionally reads ~/.kimi/config and modifies PATH. The net effect is a persistent remote-controlled channel giving the paired remote party host-level RCE on the installer's machine via the AI agent tool loop, plus a persistent lowering of a separate vendor tool's safety prompts.
Not rated by the source.
0.2.45, 0.2.46, 0.2.47, 0.2.48, 0.2.49, 0.2.50, 0.2.51, 0.2.52, 0.2.53, 0.2.55, 0.2.56, 0.2.58None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0