Which versions of devplatform-nx-stylelint are malicious?

The following npm versions of devplatform-nx-stylelint are flagged malicious: 35.6.9. Treat any of these as compromised.

How do I remediate devplatform-nx-stylelint if I installed it?

devplatform-nx-stylelint is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-nx-stylelint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

devplatform-nx-stylelintnpm

devplatform-nx-stylelint is a confirmed malicious npm package (MAL-2026-12728) that typosquats a legitimate package to trick installs (malicious version 35.6.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-nx-stylelint (npm)

MAL-2026-12728

Immediate action

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

npm uninstall devplatform-nx-stylelint

What this malware does

The package presents itself as an Nx stylelint helper but its main entry require()s platform.js, which on load downloads a platform-specific executable from one of four Cloudflare Workers hosts whose names are assembled at runtime via array-join concatenation (oob-worker.cf{99-9b3,101-adf,102-baf,103-070}.workers.dev). If HTTPS retrieval fails, it reassembles the payload from base64 chunks served in DNS TXT records under sdk/ext/pkg/net.dl.wel1.ru (reading a chunk count from c.<domain> and concatenating parts from <i>.<domain>). The bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and launched detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true, stdio:"ignore"}).unref(). A marker file.analytics_state suppresses re-execution. lib/telemetry.js embeds a second copy of the same dropper (base64 chunk decoding, split "chmod"+"Sync" and cp.spawn("/bin/sh",...)) under an analytics-SDK cover story. The exported DevplatformNxStylelint class is a no-op stub; the package's only functional behavior is the dropper. Package naming impersonates the Nx stylelint ecosystem.

Malicious versions

1 flagged

35.6.9

Indicators of compromise (SHA-256)

16573678cf46c8aabbd843cd3bbbbe258474f3768d15ad6f1178921b6ad964bf

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-nx-stylelint (version 35.6.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-nx-stylelint across your stack and pipelines.
If you installed it — respond
devplatform-nx-stylelint is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-nx-stylelint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-nx-stylelint 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-nx-stylelint 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-nx-stylelint on npm has been identified as a malicious package (version 35.6.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015043

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-nx-stylelint-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