Which versions of @flexmr/ui are malicious?

The following npm versions of @flexmr/ui are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @flexmr/ui if I installed it?

@flexmr/ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @flexmr/ui — how do I know if it already compromised me?

If @flexmr/ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @flexmr/ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @flexmr/ui (version 99.99.99).

Malicious package

@flexmr/uinpm

Advisory published Oct 13, 2026Updated Oct 15, 2026

@flexmr/ui is a confirmed malicious npm package (MAL-2026-17879) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @flexmr/ui (npm)

MAL-2026-17879

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @flexmr/ui

What this malware does

@flexmr/[email protected] runs node beacon.js preinstall, node beacon.js install, and node beacon.js postinstall during installation. These lifecycle scripts send the package name, lifecycle event, a fixed token, and host identity details to 177.7.60.239:48080 and encode the hostname in a DNS query under oob.recon.dev, probing whether a build resolves the package from the public npm registry; it was published on 2026-10-13.

Malicious versions

1 flagged

99.99.99

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @flexmr/ui (version 99.99.99).
If you installed it — respond
@flexmr/ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @flexmr/ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @flexmr/ui on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

npmjs.com

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @flexmr/ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database