Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

stylelint-recommendednpm

Malicious code in stylelint-recommended (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-872
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall stylelint-recommended

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

8 flagged
13.10.213.10.313.10.413.10.513.10.613.10.713.10.813.10.9

Indicators of compromise (SHA-256)

83155e9880bf60f9dcf9f3951829660ae61a0e56eb8e58353715d78ab04a2d47
d3f0d274dda57eb9c09967bc0bfad1709fd8ddcbf3ec4c0e7e9828826e6d0d9a
aa1d868f9efe36ec80fbae9d7b1dea530e98aa87e99d2b4ca67776f24137abba

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stylelint-recommended (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stylelint-recommended across your stack and pipelines.

  2. If you installed it — respond

    Remove stylelint-recommended 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.

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks stylelint-recommended 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. stylelint-recommended on npm has been identified as a malicious package (versions 13.10.2, 13.10.3, 13.10.4, 13.10.5, 13.10.6, 13.10.7, 13.10.8, 13.10.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-prwr-p62p-3qr2RLMA-2026-01598

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks stylelint-recommended-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.

stylelint-recommended (npm) malicious package — MAL-2026-872 | O3 Security