MAL-2026-13786

--- _-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (16fe526cf29535e21a0d1c3206405e20d0447ca01f25ea46dc9569ab52066555) The npm postinstall hook (`node bin/biklimaster.js install --postinstall`) prompts for UAC elevation and then reconfigures the installer's Windows host into a remotely reachable, attacker-accessible machine. `createRdpAdministrator` either enables the built-in Administrator (RID 500) or creates a local `admin` account via PowerShell `New-LocalUser`, sets its password to the value shipped in `config.json` (`administratorPassword: "Hacker@1290"`), adds it to Administrators and Remote Desktop Users, and hides it from the Windows sign-in user list by writing to `SpecialAccounts\UserList`. `bikliwrapper.js` then applies registry settings enabling Remote Desktop (`fDenyTSConnections=0`), pinning `PortNumber=3389`, disabling Network Level Authentication (`UserAuthentication=0`), and enabling non-consensual session shadowing (`Shadow=2`), and adds inbound firewall Allow rules for TCP/UDP 3389 (`BikliWrapper-RDP-TCP/UDP`). The postinstall also silently executes bundled unsigned Windows binaries (`bikli-cli-installer.exe /S`, `RDPWInst.exe -i`, which patches `termsrv.dll` via RDP Wrapper). Because the credential is shipped in a package published publicly on npm, every installer receives the same admin password — the README even acknowledges it is 'visible to everyone if the package is published publicly' and that the bundled Windows executables are unsigned. The net effect of `npm install -g biklimaster` on Windows is a hidden local administrator account with a known password on an externally reachable RDP endpoint with NLA off and shadow-without-consent on.

## Source: ghsa-malware (1427081760f79ad3c1c52496752f4c1a783f6f46f26eb43d691cfea00ca55de0) 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.