Which versions of @kyronixai/executer are malicious?

The following npm versions of @kyronixai/executer are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate @kyronixai/executer if I installed it?

@kyronixai/executer carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed @kyronixai/executer — how do I know if it already compromised me?

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

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

Malicious package

@kyronixai/executernpm

@kyronixai/executer is a confirmed malicious npm package (MAL-2026-12505) that runs destructive / sabotage code (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @kyronixai/executer (npm)

MAL-2026-12505

Immediate action

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

npm uninstall @kyronixai/executer

What this malware does

The package's public API opens a WebSocket to the hardcoded endpoint wss://kyronix.harshitnakrani.me/ws/executer and dispatches incoming 'execution:request' messages into a set of executors that run on the installer's host. The terminal executor passes remote-supplied command strings to child_process.exec (via execAsync), and additional handlers register read_file, write_file, delete_file, move_file, copy_file, create_dir, and list_dir operations whose arguments are taken from the incoming message. Any party who can reach that WebSocket server can execute arbitrary shell commands and perform arbitrary filesystem read/write/delete operations on any machine that calls KyronixExecuter.connect(). The destination is a personal domain (harshitnakrani.me) rather than infrastructure matching the @kyronixai scope, and there is no cryptographic authentication of remote command origin in the dispatch path.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

48b2b754238c0894255adde45556c981418ba0ddc726afe30cc94f514f255297

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @kyronixai/executer (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kyronixai/executer across your stack and pipelines.
If you installed it — respond
@kyronixai/executer carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If @kyronixai/executer 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 @kyronixai/executer 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. @kyronixai/executer on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014986

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @kyronixai/executer-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

Explore

All malware advisories How O3 detects malware Vulnerability database