bikliwrappernpm
Advisory published Updated
bikliwrapper is a confirmed malicious npm package (MAL-2026-13788) that opens a backdoor for remote access (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 bikliwrapper (npm)
What this malware does
bikliwrapper's npm postinstall script re-executes itself with UAC elevation (Start-Process -Verb RunAs -WindowStyle Hidden) and, after the single UAC prompt, reconfigures the installer's Windows host for remote access without further consent: it sets HKLM Terminal Server keys to enable RDP (fDenyTSConnections=0), disables Network Level Authentication (UserAuthentication=0), sets Shadow=2 on both RDP-Tcp and the shadow policy key (full remote shadowing of the interactive user's session without prompting the user), opens inbound Windows Firewall rules on TCP/UDP 3389, and executes the bundled payload/RDPWInst.exe (RDP Wrapper v1.6.2, ~1.4 MB Delphi PE) with -i under elevated privilege to patch termsrv.dll so concurrent/shadow sessions are permitted. The bundled binary is not verified against a publisher signature. The combined post-install state — RDP listening, NLA off, shadow-without-permission enabled, firewall opened, TermService patched — is a persistent unauthenticated remote-control channel into the installer's machine established as a side effect of npm install.
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
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for bikliwrapper (3 malicious versions).
If you installed it — respond
bikliwrapper establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bikliwrapper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bikliwrapper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.