Which versions of helixbox-connect are malicious?

The following npm versions of helixbox-connect are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate helixbox-connect if I installed it?

helixbox-connect is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed helixbox-connect — how do I know if it already compromised me?

If helixbox-connect 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 helixbox-connect part of a known attack campaign?

Yes — helixbox-connect is associated with the IN-MAL-2026-014975 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 helixbox-connect 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 helixbox-connect (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helixbox-connect across your stack and pipelines.

Malicious package

helixbox-connectnpm

helixbox-connect is a confirmed malicious npm package (MAL-2026-12793) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in helixbox-connect (npm)

MAL-2026-12793

Immediate action

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

npm uninstall helixbox-connect

What this malware does

The helixbox-connect bin opens a WebSocket to the hardcoded relay wss://helixbox-relay.onrender.com and dispatches messages from the peer into local execution primitives on the installer's host. A terminal.input handler forwards peer-supplied bytes directly into the stdin of a spawned interactive shell (/bin/bash -i on Unix, powershell.exe on Windows), giving the remote party full command execution under the running user. fs.read/fs.write/fs.ls/fs.stat handlers accept absolute paths from the peer without confinement (resolvePath returns the path as-is; an in-source comment states the app can browse and edit anywhere on the machine), enabling arbitrary read and overwrite of files including SSH keys, shell RCs, and credential stores. An ai.prompt handler spawns any locally installed agentic coding CLI (codex/claude/opencode) with prompt text supplied by the peer, invoking codex with exec --skip-git-repo-check so the remote party can drive the local AI agent to run further code under the user's credentials. dist/plain/agent.js issues POST/fetch to https://helixbox-relay.onrender.com for session control. Whoever controls the paired relay session obtains full-host remote code execution and unrestricted filesystem access on the installer's machine.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

45774464be73a3ba586a4eb9af5a89b3f2439a4f49a80c0b69eb4668cfcf7f89

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for helixbox-connect (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helixbox-connect across your stack and pipelines.
If you installed it — respond
helixbox-connect is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If helixbox-connect 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 helixbox-connect 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. helixbox-connect on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014975

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks helixbox-connect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database