Which versions of @cyberrant-rantai/rantai are malicious?

The following npm versions of @cyberrant-rantai/rantai are flagged malicious: 1.0.15. Treat any of these as compromised.

How do I remediate @cyberrant-rantai/rantai if I installed it?

Remove @cyberrant-rantai/rantai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @cyberrant-rantai/rantai — how do I know if it already compromised me?

If @cyberrant-rantai/rantai 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 @cyberrant-rantai/rantai part of a known attack campaign?

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

Malicious package

@cyberrant-rantai/rantainpm

Malicious code in @cyberrant-rantai/rantai (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10709

Immediate action

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

npm uninstall @cyberrant-rantai/rantai

What this malware does

runtime/local_agent.py opens a Socket.IO client connection to a hardcoded server at https://app.cyberrant.org (overridable via $SERVER_URL) and registers an 'execute_command' handler that dispatches incoming {command, args} payloads to cli.task_executor.TaskExecutor with task_type defaulting to 'shell', giving the remote server arbitrary shell execution on the host running the agent. runtime/cli/web_connector.py enrolls the CLI itself against CYBERRANT_WS_URL (default https://api.cyberrant.org) by emitting a 'register_lea' (Local Execution Agent) event and subscribing to 'execute_command', mirroring the same remote-execution channel from the user-facing CLI. Whoever controls those endpoints (or gains access to that channel) can issue shell commands that run under the installing user's account.

Malicious versions

1 flagged

1.0.15

Indicators of compromise (SHA-256)

41d1dbf6fb83f9a7c4c4b94ee40255e86910714400e249fec55b031e809c92bd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @cyberrant-rantai/rantai (version 1.0.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cyberrant-rantai/rantai across your stack and pipelines.
If you installed it — respond
Remove @cyberrant-rantai/rantai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @cyberrant-rantai/rantai 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 @cyberrant-rantai/rantai 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. @cyberrant-rantai/rantai on npm has been identified as a malicious package (version 1.0.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010785

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @cyberrant-rantai/rantai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring