Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@platform-services/hrm-mfe-corenpm

Advisory published Updated

@platform-services/hrm-mfe-core is a confirmed malicious npm package (MAL-2026-18091) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @platform-services/hrm-mfe-core (npm)

MAL-2026-18091
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @platform-services/hrm-mfe-core

What this malware does

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.

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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

c7552efe145088950a0df7a5c63da92a309a040fba2062a4d32bb59cadc9ec47
6340950b2d19371534634bc33af5c0b785b1fa105a5c1084c5689879c4b03da8

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @platform-services/hrm-mfe-core (version 99.9.1).

  2. If you installed it — respond

    Remove @platform-services/hrm-mfe-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @platform-services/hrm-mfe-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @platform-services/hrm-mfe-core on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021576

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @platform-services/hrm-mfe-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@platform-services/hrm-mfe-core (npm) malicious package — MAL-2026-18091 | O3 Security