Which versions of devplatform-eslint-plugin-nx are malicious?

The following npm versions of devplatform-eslint-plugin-nx are flagged malicious: 35.6.5. Treat any of these as compromised.

How do I remediate devplatform-eslint-plugin-nx if I installed it?

devplatform-eslint-plugin-nx establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed devplatform-eslint-plugin-nx — how do I know if it already compromised me?

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

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

Malicious package

devplatform-eslint-plugin-nxnpm

devplatform-eslint-plugin-nx is a confirmed malicious npm package (MAL-2026-12710) that opens a backdoor for remote access (malicious version 35.6.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-eslint-plugin-nx (npm)

MAL-2026-12710

Immediate action

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

npm uninstall devplatform-eslint-plugin-nx

What this malware does

[email protected] is a typosquat lure targeting @nx/eslint-plugin. On require() of the package, index.js loads runtime.js which asynchronously downloads a per-platform binary from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT chunked-base64 fallback across sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The payload is written to /tmp or %TEMP% under a disguised name (dotnet_diag<suffix>.exe on Windows,.cache_<suffix> on Unix), chmod 0755'd on non-Windows, and detached-spawned via /bin/sh -c or cmd.exe /c start. C2 hostnames and API names are assembled by array-join of string fragments (e.g. ["oob-worker.cf101","-adf.worker","s.d","ev"].join("") and fs["chmod"+"Sync"]) to evade static detection. A telemetry cover story (opt-out checks for DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK, a cooldown stamp at /tmp/.analytics_state) is layered over the dropper. A second, currently unreferenced but shipped bundle lib/telemetry.js contains the same dropper primitives.

Malicious versions

1 flagged

35.6.5

Indicators of compromise (SHA-256)

35adb61664d8a7067c4ace2c143ed75e5e316dcd5365201ac8614ef9ff07e668

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-eslint-plugin-nx (version 35.6.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-eslint-plugin-nx across your stack and pipelines.
If you installed it — respond
devplatform-eslint-plugin-nx establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-eslint-plugin-nx 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 devplatform-eslint-plugin-nx 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. devplatform-eslint-plugin-nx on npm has been identified as a malicious package (version 35.6.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015062

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-eslint-plugin-nx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database