What does the @flexmr/utils malware do?

The OpenSSF Package Analysis project identified '@flexmr/utils' @ 3.0.12 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of @flexmr/utils are malicious?

The following npm versions of @flexmr/utils are flagged malicious: 1.0.0, 3.0.12. Treat any of these as compromised.

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

Remove @flexmr/utils 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.

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

If @flexmr/utils 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/utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @flexmr/utils (2 malicious versions).

Malicious package

@flexmr/utilsnpm

Advisory published Oct 14, 2026Updated Oct 15, 2026

@flexmr/utils is a confirmed malicious npm package (MAL-2026-17888) that executes malicious code on install (malicious versions 1.0.0, 3.0.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @flexmr/utils (npm)

MAL-2026-17888

Immediate action

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

npm uninstall @flexmr/utils

What this malware does

The OpenSSF Package Analysis project identified '@flexmr/utils' @ 3.0.12 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.03.0.12

Indicators of compromise (SHA-256)

ccf04862b6c4575628dc879f9582eb1a359f1b50522eed7372847de34caa2825

fc751fb286e3a288e498adfc3b9b936c1ff40270a1c342047a7d778ce24936f4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @flexmr/utils (2 malicious versions).
If you installed it — respond
Remove @flexmr/utils 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.
Did it already run?
If @flexmr/utils 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/utils on npm has been identified as a malicious package (versions 1.0.0, 3.0.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @flexmr/utils-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database