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

pluxee-design-systemnpm

Malicious code in pluxee-design-system (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191502
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pluxee-design-system

What this malware does

The package pluxee-design-system 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

701f52cd229baaf8a44c372915a6bdbcc5510c156fb75c21d23c932d51ccde2f
340fa91d269a36c44ef91b31d56c196802243775e78dbcffe5c4f7fc122bb1b0

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 pluxee-design-system (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pluxee-design-system across your stack and pipelines.

  2. If you installed it — respond

    Remove pluxee-design-system 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 pluxee-design-system 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 pluxee-design-system 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. pluxee-design-system on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h25r-4pmf-r6mf

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks pluxee-design-system-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.

pluxee-design-system (npm) malicious package — MAL-2025-191502 | O3 Security