Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

eslint-config-sdknpm

Malicious code in eslint-config-sdk (npm) Remove it immediately and rotate any exposed credentials.

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-config-sdk (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-sdk across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If eslint-config-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks eslint-config-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

eslint-config-sdk (npm) malicious package — MAL-2025-192952 | O3 Security