Which versions of devplatform-stylelint-config are malicious?

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

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

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

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

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

Malicious package

devplatform-stylelint-confignpm

devplatform-stylelint-config is a confirmed malicious npm package (MAL-2026-13548) that executes malicious code on install (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-stylelint-config (npm)

MAL-2026-13548

Immediate action

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

npm uninstall devplatform-stylelint-config

What this malware does

The package is published as 'devplatform-stylelint-config' with description 'environment config reader' and exposes a trivial ConfigLoader from index.js, but index.js also require()s./setup.js which runs at library load. setup.js assembles Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) and dl.wel1.ru subdomains (sdk./ext./pkg./net.) from array joins to defeat literal string matching, with a DNS-TXT chunked base64 fallback channel (c.<domain> count plus <i>.<domain> chunks via resolveTxt). It downloads a platform-specific binary over HTTPS, writes it to a hidden temp path (/tmp/.cache_<hex> or %TEMP%/dotnet_diag_<hex>.exe), chmods 0755, and detaches it via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() (with a cmd equivalent on Windows). No hash or signature verification is performed. Cover-story naming ('analytics_state', a DISABLE_TELEMETRY gate) and the package name/description mismatch conceal the payload.

Malicious versions

1 flagged

35.7.4

Indicators of compromise (SHA-256)

0d5c417e542790e2e91860f8383960eecead75556b747c0fdc91227c3228f514

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-017028

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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