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

pc-experience-fe-componentsnpm

pc-experience-fe-components is a confirmed malicious npm package (MAL-2025-49342) that executes malicious code on install (malicious versions 99.0.0, 99.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pc-experience-fe-components (npm)

MAL-2025-49342
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pc-experience-fe-components

What this malware does

The package pc-experience-fe-components was found to contain malicious code.

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.

Malicious versions

2 flagged
99.0.099.1.2

Indicators of compromise (SHA-256)

8257ed048a6a07820b94cb55bada5ee260ab483c75647da8c506236aa890e7e5
fddb980aa93c2d431c4ec7d642d3335095b7f2bdd688a1debb6f549f170b3c15
db6db918be0e8755329704612af64452467ea27500dd9fe4fc19f58da0e72e68

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pc-experience-fe-components (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pc-experience-fe-components across your stack and pipelines.

  2. If you installed it — respond

    Remove pc-experience-fe-components 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 pc-experience-fe-components was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks pc-experience-fe-components before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pc-experience-fe-components on npm has been identified as a malicious package (versions 99.0.0, 99.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgv3-2247-x93pRLMA-2025-05913

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks pc-experience-fe-components-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

pc-experience-fe-components (npm) malicious package — MAL-2025-49342 | O3 Security