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

@pes-ui/componentsnpm

Malicious code in @pes-ui/components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2591
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @pes-ui/components

What this malware does

The package @pes-ui/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

1 flagged
99.9.0

Indicators of compromise (SHA-256)

b702a08c2c8f56831c1cb8052a99ace60d740f65c91a8879d3e1d81a886c96ef
a840430867fa11d0454fdf565872ab6bfa5700ef9514a309dbcfa53b57472267
3c86f728ffc679c2767dd34f810c998e9e7fa49098d757ee8a3ba6b050f1754f

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 @pes-ui/components (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @pes-ui/components across your stack and pipelines.

  2. If you installed it — respond

    Remove @pes-ui/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 @pes-ui/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 @pes-ui/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. @pes-ui/components on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ww6q-42qg-c93cRLMA-2026-01863

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @pes-ui/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.