Which versions of stylelint-preference are malicious?

The following npm versions of stylelint-preference are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate stylelint-preference if I installed it?

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

If stylelint-preference 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.

Is stylelint-preference part of a known attack campaign?

Yes — stylelint-preference is associated with the RLMA-2026-01597 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 stylelint-preference across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stylelint-preference (version 1.0.8).

Malicious package

stylelint-preferencenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in stylelint-preference (npm)

MAL-2026-1859

Immediate action

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

npm uninstall stylelint-preference

What this malware does

The package stylelint-preference was found to contain malicious code.

Malicious versions

1 flagged

1.0.8

Indicators of compromise (SHA-256)

4bca6f7aaa7d2850efe7dbd4daee8749e8cf10f726b10746fb8dd801e46e6b71

9bcab12465d2562c808eb72d7be466706aa9f7074bcbb6f7a56744484ecfe7d9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01597

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks stylelint-preference-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