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

fq-uinpm

fq-ui is a confirmed malicious npm package (MAL-2024-2393) that executes malicious code on install (malicious versions 1.0.0-dev, 1.0.2-dev, 1.541.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fq-ui (npm)

MAL-2024-2393
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fq-ui

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

17 flagged
1.0.0-dev1.0.2-dev1.541.11.642.22.542.12.643.23.543.13.644.24.544.14.645.25.545.15.646.26.647.27.648.28.649.29.650.222.0.0

Indicators of compromise (SHA-256)

cb9ec7de8c2b29249ddde70bf326ef9ebcb251f6a7dd060348717a2e1649b515
62969e15cffdc682f0d693211bfeba7e5f3b72ec101f7e9095c7d4841d545bc6
2ce1fb799433153eff547fb7ee245b4f7d0e230c86476ddd6ec16bbb7638abc0
560daca9e0425c684eadaefa3acb389babb6aa31e931f76b1f794405c8254ff5

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

  2. If you installed it — respond

    Remove fq-ui 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 fq-ui 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 fq-ui 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. fq-ui on npm has been identified as a malicious package (versions 1.0.0-dev, 1.0.2-dev, 1.541.1, 1.642.2, 2.542.1, 2.643.2, 3.543.1, 3.644.2, and 9 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-01051RLUA-2024-06610GHSA-8gfp-4jvf-4x9hRLUA-2025-05797

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks fq-ui-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

fq-ui (npm) malicious package — MAL-2024-2393 | O3 Security