NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

sw-pluginernpm

Advisory published Updated

sw-pluginer is a confirmed malicious npm package (MAL-2026-14211) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sw-pluginer (npm)

MAL-2026-14211
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sw-pluginer

What this malware does

sw-pluginer presents itself as a Tailwind plugin for service worker registration, but its main export — invoked when Tailwind processes its config via require('sw-pluginer') — reads a URL from a staged file at node_modules/.bin/manifest.json, performs an HTTP GET to that URL, and passes the response body directly to eval() in the Node build process. The staging file is written by a separate dropper component and is unlinked after being read, hiding the payload destination from static inspection of the sw-pluginer tarball itself. The fetched code is not pinned, hashed, or signature-verified, and it is executed in the developer's Node environment (not in a browser as service worker code) — so whoever controls the staged manifest.json obtains arbitrary code execution on the developer machine at build time. The self-deleting indirection through node_modules/.bin/manifest.json plus eval of unverified network-fetched JavaScript is a covert dropper mechanism, not service worker registration.

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

5 flagged
1.0.01.0.11.0.21.1.01.2.0

Indicators of compromise (SHA-256)

04cb9419a7170f7f1d55a8515c8d931d0a388fdf9b55c692a72a3f447539b650
38427a19b5e267273200d4dc05d0b9a60f0a38bfe7916adaaeb90338af5f1b06
4774f9e54911d1231788224ac0d528431050050cbcc8a053f1f40eb6e73b8ff1
b5f6a7d297091f57fe43af57f951f3acc3f82e51363747e84b87113c13e76212
cc3a59d3a151fdca61663452e132622d9f9201013e53a4f57805845c290c5551
f26a48c2809dda4d8d5fa065b6f1ba3a6e485e09f4f040341cb43890f32de0fd

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for sw-pluginer (5 malicious versions).

  2. If you installed it — respond

    Remove sw-pluginer 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 sw-pluginer 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. sw-pluginer on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018301IN-MAL-2026-018300IN-MAL-2026-018304IN-MAL-2026-018303IN-MAL-2026-018302GHSA-38qc-cchj-49wq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sw-pluginer-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.

Explore

sw-pluginer (npm) malicious package — MAL-2026-14211 | O3 Security