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

@account-portal/ui-toolkit-reactnpm

@account-portal/ui-toolkit-react is a confirmed malicious npm package (MAL-2025-47130) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @account-portal/ui-toolkit-react (npm)

MAL-2025-47130
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @account-portal/ui-toolkit-react

What this malware does

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)

8071d62a3309d3670bd962154aedbcb3fcfad9e85579f6fe36be0fccbd5feb2c
6675d32f78174a49b42271b9b18e4fd987d4636d63a98e3678f051e4d3a7b2d9
37d0c85c7eeca63a5a8b7d84d7d9d3bcb7a332e3a745d082467798cc5a06dc3a
4ca9869eb19ca096fd7d2dc834afcbd64bc3f4bd9e0048289919064ca93890d2
87741d7046b067ebc0c453c5af6fad654ce5cde13646938767da8bb074ab0162

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 @account-portal/ui-toolkit-react (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 @account-portal/ui-toolkit-react across your stack and pipelines.

  2. If you installed it — respond

    Remove @account-portal/ui-toolkit-react 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 @account-portal/ui-toolkit-react 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 @account-portal/ui-toolkit-react 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. @account-portal/ui-toolkit-react 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-fpvj-gx33-5665RLMA-2025-04828RLUA-2026-00962

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @account-portal/ui-toolkit-react-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

@account-portal/ui-toolkit-react (npm) malicious package — MAL-2025-47130 | O3 Security