Malicious code in @ikbal_fadilah_vanexa01/vanexa-agent (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13364
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (52b1477c5187703dab87d6be6933d62de4c4244ab3340586f85b530e05470aa1) Package ships an agent daemon (`vanexa-agent start`, entry `bin/vanexa-agent.js`) that receives commands from a remote phone app and executes them on the installer's host via `child_process`/`spawn`, including `powershell.exe` and inline JS/Python evaluation. Rather than the LAN-only WebSocket architecture described in the README (which claims BYOK with `no middleman`), the compiled bundle hardcodes two Cloudflare Workers endpoints — `vanexa-agent-relay.hanazaki542.workers.dev` and `vanexa-ai-proxy.hanazaki542.workers.dev` — hosted on a personal Cloudflare account (`hanazaki542`) that does not match the npm publisher (`ikbalsakata500445jensen`). Commands from the phone client and, via the AI proxy path, user-supplied prompt content and API tokens transit this third-party intermediary before reaching the local execution sinks on the installer's machine. The primary runtime is shipped as V8 bytecode (`dist/bundle.jsc`) produced from `dist/bundle.cjs` at postinstall via `bytenode.compileFile`, and the bin entry loads that bytecode with `require(bytecodePath)`, reducing auditability of the network-driven exec path. The combination — network-sourced commands flowing into local shell/child_process, a hardcoded author-controlled relay whose ownership does not match the publisher, and a bytecode-compiled payload — makes normal operator use of this agent equivalent to granting the relay operator remote command execution on the installer's host.
- Source published
- 5 Aug 2026 18:16:17 UTC
- Source modified
- 6 Aug 2026 14:34:47 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.