NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@teale.io/eslint-confignpm

Advisory published Updated

@teale.io/eslint-config is a confirmed malicious npm package (MAL-2026-2066) that steals credentials and exfiltrates sensitive data (malicious versions 1.8.9, 1.8.10, 1.8.11…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @teale.io/eslint-config (npm)

MAL-2026-2066
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @teale.io/eslint-config

What this malware does

The package @teale.io/eslint-config was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

8 flagged
1.8.91.8.101.8.111.8.121.8.131.8.141.8.151.8.16

Indicators of compromise (SHA-256)

acc79b4637cfd4a80009ec5b78dc58e8ae9096c1366936651cf94fe78abb042e
284588dababf2ba34a063a6b82abf5443b1636ece9f11895620ab5bab1e6b515
28691afbcafd3f47a795fc5c8f108928a15773d5e1225c753fc59e8340056bf0

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @teale.io/eslint-config (8 malicious versions).

  2. If you installed it — respond

    @teale.io/eslint-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @teale.io/eslint-config 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. @teale.io/eslint-config on npm has been identified as a malicious package (versions 1.8.9, 1.8.10, 1.8.11, 1.8.12, 1.8.13, 1.8.14, 1.8.15, 1.8.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7h5g-m989-54j2

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @teale.io/eslint-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@teale.io/eslint-config (npm) malicious package — MAL-2026-2066 | O3 Security