Which versions of shreddit.styles are malicious?

The following npm versions of shreddit.styles are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate shreddit.styles if I installed it?

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

If shreddit.styles 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 shreddit.styles part of a known attack campaign?

Yes — shreddit.styles is associated with the GHSA-jfvh-jh3m-75wr, RLMA-2026-01570 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 shreddit.styles 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 shreddit.styles (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shreddit.styles across your stack and pipelines.

Malicious package

shreddit.stylesnpm

Malicious code in shreddit.styles (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-180

Immediate action

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

npm uninstall shreddit.styles

What this malware does

The package shreddit.styles 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

1 flagged

9.9.9

Indicators of compromise (SHA-256)

2c65bd95325c1ee64e6f0b45b33b62af1973c49ed5c4eed64c725d08a51201bb

8cce1be43bf6e26a99a58a3f011f71a44d06f3227d24bf2274c9f3b41c0fc3de

6edf769b65119e82b7499fdde914c617a0023b5d6223823f4dadc68d68b4dacd

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 shreddit.styles (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shreddit.styles across your stack and pipelines.
If you installed it — respond
Remove shreddit.styles 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 shreddit.styles 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 shreddit.styles 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. shreddit.styles on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jfvh-jh3m-75wrRLMA-2026-01570

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks shreddit.styles-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