Which versions of sfx-data are malicious?

The following npm versions of sfx-data are flagged malicious: 2.1.0, 2.1.1, 99.0.0. Treat any of these as compromised.

How do I remediate sfx-data if I installed it?

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

If sfx-data 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 sfx-data part of a known attack campaign?

Yes — sfx-data is associated with the RLMA-2026-02040 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 sfx-data across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sfx-data (3 malicious versions).

Malicious package

sfx-datanpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

sfx-data is a confirmed malicious npm package (MAL-2026-2801) that executes malicious code on install (malicious versions 2.1.0, 2.1.1, 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sfx-data (npm)

MAL-2026-2801

Immediate action

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

npm uninstall sfx-data

What this malware does

The package sfx-data was found to contain malicious code.

Malicious versions

3 flagged

2.1.02.1.199.0.0

Indicators of compromise (SHA-256)

545440223f73c3799538b3733680f9b3031bd6fb747dc967a91a9676c5ceef1e

d3fe291f014f24a669e43d0092e768f822241c223899812aeeb652ade2dcc63f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02040

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sfx-data-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