Which versions of eslint-plugin-skywagon-web are malicious?

The following npm versions of eslint-plugin-skywagon-web are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate eslint-plugin-skywagon-web if I installed it?

eslint-plugin-skywagon-web 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-plugin-skywagon-web — how do I know if it already compromised me?

If eslint-plugin-skywagon-web 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-plugin-skywagon-web part of a known attack campaign?

Yes — eslint-plugin-skywagon-web is associated with the IN-MAL-2026-020582 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-plugin-skywagon-web 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-plugin-skywagon-web (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-skywagon-web across your stack and pipelines.

Malicious package

eslint-plugin-skywagon-webnpm

eslint-plugin-skywagon-web is a confirmed malicious npm package (MAL-2026-17215) that steals credentials and exfiltrates sensitive data (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-skywagon-web (npm)

MAL-2026-17215

Immediate action

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

npm uninstall eslint-plugin-skywagon-web

What this malware does

[email protected] ships an index.js that is executed via a preinstall lifecycle script on npm install. The script collects installer-side identifiers — os.hostname(), os.userInfo().username, os.homedir(), process.cwd(), dns.getServers(), and the contents of the package's package.json — and POSTs them over HTTPS to the hardcoded external collector eo1blcdjptwydyq.m.pipedream.net. A source comment ("replace burpcollaborator.net with Interactsh or pipedream") shows the file is a dependency-confusion exfiltration template repurposed as a live payload. The implausibly high version number (100.0.0) is consistent with a dependency-confusion lure intended to override an internal package of the same name during resolution.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

3c5d134d2e79b24ed65d2998520db05b5cc86b251ae579a6d8cec6d8fe02340f

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-plugin-skywagon-web (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-skywagon-web across your stack and pipelines.
If you installed it — respond
eslint-plugin-skywagon-web 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-plugin-skywagon-web 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-plugin-skywagon-web 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-plugin-skywagon-web on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020582

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eslint-plugin-skywagon-web-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

Explore

All malware advisories How O3 detects malware Vulnerability database