Which versions of @ikbal_fadilah_vanexa01/vanexa-agent are malicious?

The following npm versions of @ikbal_fadilah_vanexa01/vanexa-agent are flagged malicious: 1.3.10. Treat any of these as compromised.

How do I remediate @ikbal_fadilah_vanexa01/vanexa-agent if I installed it?

@ikbal_fadilah_vanexa01/vanexa-agent establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @ikbal_fadilah_vanexa01/vanexa-agent — how do I know if it already compromised me?

If @ikbal_fadilah_vanexa01/vanexa-agent was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @ikbal_fadilah_vanexa01/vanexa-agent part of a known attack campaign?

Yes — @ikbal_fadilah_vanexa01/vanexa-agent is associated with the IN-MAL-2026-015847 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ikbal_fadilah_vanexa01/vanexa-agent across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ikbal_fadilah_vanexa01/vanexa-agent (version 1.3.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikbal_fadilah_vanexa01/vanexa-agent across your stack and pipelines.

Malicious package

@ikbal_fadilah_vanexa01/vanexa-agentnpm

@ikbal_fadilah_vanexa01/vanexa-agent is a confirmed malicious npm package (MAL-2026-13364) that opens a backdoor for remote access (malicious version 1.3.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ikbal_fadilah_vanexa01/vanexa-agent (npm)

MAL-2026-13364

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ikbal_fadilah_vanexa01/vanexa-agent

What this malware does

The bundled daemon in dist/bundle.cjs opens an outbound WebSocket to a hardcoded relay at vanexa-agent-relay.hanazaki542.workers.dev (an author-controlled Cloudflare Workers subdomain), parses inbound JSON messages, and dispatches messages of type 'task_request' to an agent that exposes a 'terminal.exec' tool spawning arbitrary shell commands on the installer's host. The relay URL is not effectively user-configurable: attempts to point at a different vanexa-agent-relay.workers.dev host are rewritten back to hanazaki542.workers.dev. Anyone controlling that relay can drive shell execution on any host running the daemon, giving persistent remote command-and-control over the installer's machine. Separately, when no API key is configured the client posts full chat messages plus a stable device hash to a second hardcoded author-controlled endpoint (vanexa-ai-proxy.hanazaki542.workers.dev) instead of the user's chosen LLM provider, silently relaying user prompt content and a device identifier through the author's infrastructure.

Malicious versions

1 flagged

1.3.10

Indicators of compromise (SHA-256)

481daae8905848ad63e1ea0680645761de3594c5eaa017e9e6f6ea8fe6e2282e

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ikbal_fadilah_vanexa01/vanexa-agent (version 1.3.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikbal_fadilah_vanexa01/vanexa-agent across your stack and pipelines.
If you installed it — respond
@ikbal_fadilah_vanexa01/vanexa-agent establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @ikbal_fadilah_vanexa01/vanexa-agent was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ikbal_fadilah_vanexa01/vanexa-agent before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ikbal_fadilah_vanexa01/vanexa-agent on npm has been identified as a malicious package (version 1.3.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015847

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ikbal_fadilah_vanexa01/vanexa-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database