Which versions of eslint-config-skynet are malicious?

Every published version of eslint-config-skynet on npm is considered malicious. Remove the package entirely.

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

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

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

How do I find eslint-config-skynet across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eslint-config-skynet (all published versions).

Malicious package

eslint-config-skynetnpm

Advisory published Jan 2, 2026Updated Jan 2, 2026

eslint-config-skynet is a confirmed malicious npm package (MAL-2026-15) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-config-skynet (npm)

MAL-2026-15

Immediate action

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

npm uninstall eslint-config-skynet

What this malware does

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

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b7e73967dab61cd67b0f3c96ab2c059e3fc5405fb451c62165d429bfbcf1e3df

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

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