jkbnwsdf8npm
jkbnwsdf8 is a confirmed malicious npm package (MAL-2026-13818) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in jkbnwsdf8 (npm)
What this malware does
The package contains a single file, index.html, declared as the package main. The HTML is styled as a Cloudflare Turnstile 'Just a moment...' challenge page and contains obfuscator.io-encoded JavaScript that, after a Turnstile callback, constructs a redirect URL from a fragmented literal ('https://lo' + <decoded> + /) and calls window.location.assign(targetUrl), forwarding the caller's query string. There is no package.json lifecycle script (no preinstall/install/postinstall/prepare) and no JavaScript main entry, so npm install and require() of this package do not execute any code on the installer's machine — Node cannot execute HTML. The redirect only fires against browser end-users who load the HTML through an npm CDN such as unpkg or jsdelivr, which is outside the installer-protection scope of this engine. The package is abusing npm as a static-hosting CDN for what appears to be a redirect/cloaking page and warrants a registry-abuse takedown, but it does not attack developers or build systems that install it.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 jkbnwsdf8 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jkbnwsdf8 across your stack and pipelines.
If you installed it — respond
Remove jkbnwsdf8 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 jkbnwsdf8 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 jkbnwsdf8 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 jkbnwsdf8-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.