Which versions of swiper-css-normalize are malicious?

The following npm versions of swiper-css-normalize are flagged malicious: 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14, 1.0.15, 1.0.16, 1.0.17, 1.0.18. Treat any of these as compromised.

How do I remediate swiper-css-normalize if I installed it?

swiper-css-normalize carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed swiper-css-normalize — how do I know if it already compromised me?

If swiper-css-normalize 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 swiper-css-normalize part of a known attack campaign?

Yes — swiper-css-normalize is associated with the RLMA-2026-05327, RLUA-2026-06515 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 swiper-css-normalize across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for swiper-css-normalize (16 malicious versions).

Malicious package

swiper-css-normalizenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

swiper-css-normalize is a confirmed malicious npm package (MAL-2026-7427) that runs destructive / sabotage code (malicious versions 1.0.3, 1.0.4, 1.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in swiper-css-normalize (npm)

MAL-2026-7427

Immediate action

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

npm uninstall swiper-css-normalize

Malicious versions

16 flagged

1.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.121.0.131.0.141.0.151.0.161.0.171.0.18

Indicators of compromise (SHA-256)

4cb924007b5712a1d9f45f0dbb620b29cb9e78dde85e8a7d928777537ea55d84

8649a5501ffc799a03bc766ddb6fe62584fde43df535bb27511eb5ddfd97d5d8

Detection & response playbook

Destructive / sabotage

Find it
Search your lockfiles and build artifacts for swiper-css-normalize (16 malicious versions).
If you installed it — respond
swiper-css-normalize carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If swiper-css-normalize 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. swiper-css-normalize on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05327RLUA-2026-06515

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks swiper-css-normalize-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