Which versions of flow-eslint-oxidized are malicious?

The following npm versions of flow-eslint-oxidized are flagged malicious: 0.0.1, 74.2.1. Treat any of these as compromised.

How do I remediate flow-eslint-oxidized if I installed it?

Remove flow-eslint-oxidized 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 flow-eslint-oxidized — how do I know if it already compromised me?

If flow-eslint-oxidized 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.

Is flow-eslint-oxidized part of a known attack campaign?

Yes — flow-eslint-oxidized is associated with the RLMA-2026-05541, RLUA-2026-06244 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find flow-eslint-oxidized across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for flow-eslint-oxidized (2 malicious versions).

Malicious package

flow-eslint-oxidizednpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

flow-eslint-oxidized is a confirmed malicious npm package (MAL-2026-10896) that executes malicious code on install (malicious versions 0.0.1, 74.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flow-eslint-oxidized (npm)

MAL-2026-10896

Immediate action

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

npm uninstall flow-eslint-oxidized

Malicious versions

2 flagged

0.0.174.2.1

Indicators of compromise (SHA-256)

9029240505d6978d38808b876cf68ddff7053d9b4c9689ba8d31a5d6487b946e

19be4f898165faf8705303d0f3bdb34c4fc970e770a581cc56630ad479200ba4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for flow-eslint-oxidized (2 malicious versions).
If you installed it — respond
Remove flow-eslint-oxidized 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 flow-eslint-oxidized 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. flow-eslint-oxidized on npm has been identified as a malicious package (versions 0.0.1, 74.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05541RLUA-2026-06244

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks flow-eslint-oxidized-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