If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (a3cd852fb9e34a4705cad99a8022db52461e1325daddfa1425df17bbc3b7ac08)
package.json declares a dependency `node-net-pool` whose source is a tarball URL on the `main` branch of a random third-party GitHub account (`https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz`) rather than a registry version range. On `npm install`, npm fetches whatever bytes that URL currently returns, unpinned and integrity-unchecked, and executes any lifecycle scripts contained in the fetched package. The postinstall script additionally invokes `node -e "... require('node-net-pool')..."`, so the fetched module's top-level code runs in the installer's Node process at install time. The owner account name is a random throwaway-shaped identifier unrelated to any declared publisher, and the branch is mutable so the delivered code can change at any moment without a version bump.
Source: ghsa-malware (2b60a41e21be9a24e0e335f4930860f803c86100e3cda7dee5775c7f65eb8b19)
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.