What does the kordyn malware do?

The package's main entry (index.mjs) contains a chunked base64 blob whose decoded bytes are a Windows PE64 executable (MZ/PE header confirmed, including the 'This program cannot be run in DOS mode' stub). At import time, when running under Linux with a WSL environment detected via existence of /mnt/c, the module writes this embedded binary to /mnt/c/Users/ /AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/vite-native-helper.exe. Placement into the Windows Startup folder causes the binary to auto-execute on the next Windows login of the developer whose WSL environment imported the package, giving the publisher code execution on the Windows host. The package.json advertises t

Which versions of kordyn are malicious?

The following npm versions of kordyn are flagged malicious: 0.9.16, 0.9.18. Treat any of these as compromised.

How do I remediate kordyn if I installed it?

Remove kordyn 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 kordyn — how do I know if it already compromised me?

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

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

Malicious package

kordynnpm

kordyn is a confirmed malicious npm package (MAL-2026-11139) that executes malicious code on install (malicious versions 0.9.16, 0.9.18). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kordyn (npm)

MAL-2026-11139

Immediate action

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

npm uninstall kordyn

What this malware does

The package's main entry (index.mjs) contains a chunked base64 blob whose decoded bytes are a Windows PE64 executable (MZ/PE header confirmed, including the 'This program cannot be run in DOS mode' stub). At import time, when running under Linux with a WSL environment detected via existence of /mnt/c, the module writes this embedded binary to /mnt/c/Users/<user>/AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/vite-native-helper.exe. Placement into the Windows Startup folder causes the binary to auto-execute on the next Windows login of the developer whose WSL environment imported the package, giving the publisher code execution on the Windows host. The package.json advertises the module as a 'dependency-free streak counting utility' and the README describes it as an empty placeholder; the PE payload and the WSL persistence path are entirely undocumented. The filename 'vite-native-helper.exe' is a cover-story name unrelated to the package's stated purpose.

Malicious versions

2 flagged

0.9.160.9.18

Indicators of compromise (SHA-256)

52bb92157f869a5e1da58a19c88743989d44703201f8d1df250c2543b70b6be3

69e0afd1a9b99d3cabe8090a7576a0a1e1b43fe0d1946d02995cac41751214aa

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 kordyn (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kordyn across your stack and pipelines.
If you installed it — respond
Remove kordyn 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 kordyn 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 kordyn 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. kordyn on npm has been identified as a malicious package (versions 0.9.16, 0.9.18 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010944IN-MAL-2026-010943

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kordyn-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