kordynnpm
kordyn is a confirmed malicious npm package (MAL-2026-11139) that executes malicious code on install (malicious versions 0.9.10, 0.9.11, 0.9.14…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in kordyn (npm)
What this malware does
[email protected] advertises itself in package.json and README as an unimplemented placeholder for trivial streak utilities ('Early release — placeholder. Implementation to come.'), but the tarball's declared main entry index.mjs is a 355 KB module whose bulk is a base64-encoded Windows PE executable. index.mjs imports writeFileSync, mkdirSync, readdirSync, and existsSync from 'fs' at the top level and reconstructs the embedded binary via Buffer.from(_cache, 'base64'), where _cache begins with 'TVqQAAMAAAAEAAAA//8AAL...' decoding to an MZ/PE header including the 'This program cannot be run in DOS mode' stub. Simply importing or requiring the package executes the decoding path, and the imported fs write APIs indicate the decoded PE is intended to be written to the installer's disk. The advertised functionality (streak-count helpers) has no legitimate reason to embed a native Windows executable, and the placeholder cover story is inconsistent with the shipped 355 KB opaque payload in the direction that conceals it from reviewers — the shape of a staged dropper / obfuscated loader.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kordyn (7 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
Campaign
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.