Which versions of eslint-config-service-users are malicious?

The following npm versions of eslint-config-service-users are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate eslint-config-service-users if I installed it?

eslint-config-service-users 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.

I already installed eslint-config-service-users — how do I know if it already compromised me?

If eslint-config-service-users 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.

Is eslint-config-service-users part of a known attack campaign?

Yes — eslint-config-service-users is associated with the GHSA-9h8j-g652-xrg8 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-service-users across my projects, lockfiles, and CI pipelines?

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

Malicious package

eslint-config-service-usersnpm

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

MAL-2026-2069

Immediate action

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

npm uninstall eslint-config-service-users

What this malware does

The package eslint-config-service-users 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

1 flagged

0.0.3

Indicators of compromise (SHA-256)

cca87b80d045e9648cd1154040ece50b411cc059784f6e5d6667393f9cc89973

e4e2d9cbfd1dc174c6898b4375b8d4417da80c535833d43c5a4ae977252e9269

478f247e2a5931c23c4435491033d4f6bd4f841295f06a8da202de4a6d1dcc7e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-config-service-users (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-service-users across your stack and pipelines.
If you installed it — respond
eslint-config-service-users 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.
Did it already run?
If eslint-config-service-users 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.
How O3 protects you
O3 blocks eslint-config-service-users 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-service-users on npm has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9h8j-g652-xrg8

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring