Which versions of eslint-config-sdk are malicious?

The following npm versions of eslint-config-sdk are flagged malicious: 1.0.0, 1.0.1, 1.1.2, 1.1.3, 99.0.0, 100.0.0, 101.0.1, 101.0.2, 101.0.3, 101.0.4. Treat any of these as compromised.

How do I remediate eslint-config-sdk if I installed it?

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

If eslint-config-sdk 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 eslint-config-sdk part of a known attack campaign?

Yes — eslint-config-sdk is associated with the RLMA-2026-01296 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 eslint-config-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eslint-config-sdk (10 malicious versions).

Malicious package

eslint-config-sdknpm

Advisory published Dec 27, 2025Updated Mar 19, 2026

eslint-config-sdk is a confirmed malicious npm package (MAL-2025-192952) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-config-sdk (npm)

MAL-2025-192952

Immediate action

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

npm uninstall eslint-config-sdk

What this malware does

The package eslint-config-sdk was found to contain malicious code.

The OpenSSF Package Analysis project identified 'eslint-config-sdk' @ 101.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

10 flagged

1.0.01.0.11.1.21.1.399.0.0100.0.0101.0.1101.0.2101.0.3101.0.4

Indicators of compromise (SHA-256)

f555787a619d1fb5f878d4d2bc13ec29597ef72d472ef1c2897a92de23ec1662

957e494a4b9c9985c6f16f935729cea70631deadb9f0e96f5b1dfa6675dc31bb

e71714baca3a4619a8482f00c00fbed0efcca855796a70e740d4f53a3f807003

394c5581f84c76ebac0325559f81088ed9f64d89d59c08d74ac47b4005bd3ff9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eslint-config-sdk (10 malicious versions).
If you installed it — respond
Remove eslint-config-sdk 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 eslint-config-sdk 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. eslint-config-sdk on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.1.2, 1.1.3, 99.0.0, 100.0.0, 101.0.1, 101.0.2, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01296

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-config-sdk-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