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 (6340950b2d19371534634bc33af5c0b785b1fa105a5c1084c5689879c4b03da8)
package.json declares a dependency whose key equals the package's own name, @platform-services/hrm-mfe-core, with its source set to the bare URL https://s3.amazonaws.com/static.puffnetwork.com/check-network-2.2.1.tgz instead of a registry version range. On `npm install`, npm fetches that tarball and installs whatever it contains, running any lifecycle scripts inside it, with no version pin and no integrity hash. The shipped index.js is an inert stub, so the manifest line is the entire published surface: control over the referenced S3 object (puffnetwork.com, a host unrelated to the @platform-services scope) is control over code executed on the installer. The self-named dependency key additionally gives this manifest a dependency-confusion shape against any internal package of the same name.
Source: ossf-package-analysis (c7552efe145088950a0df7a5c63da92a309a040fba2062a4d32bb59cadc9ec47)
The OpenSSF Package Analysis project identified '@platform-services/hrm-mfe-core' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.