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 (ba88629ecae2a180282c29fd385e0bb2067193f01bb3b482b550ae50765d246f)
package.json declares the package's own name in both dependencies and devDependencies pointing at http://pack.nppacks.com/npm/react-remove-properties — a plain-HTTP, non-npm-registry, unpinned URL. On `npm install`, npm fetches and installs whatever tarball is served at that mutable third-party endpoint into the installer's node_modules, giving the operator of pack.nppacks.com arbitrary-code delivery into the install. The source is not the official registry, the transport is cleartext HTTP (trivially MITM-able on any network path), the resolution is unpinned (no integrity/hash), and the host is outside npm's audit surface. A header comment in index.js labels the package as 'Security Research Testing Purpose,' but a self-label does not change the delivery mechanism.
Source: ghsa-malware (11e4c534721cad53fa6b13dae6082157793d772d31c12dbd0f0655d1064d3f77)
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.