Which versions of scdn-jquery are malicious?

The following npm versions of scdn-jquery are flagged malicious: 0.1.6. Treat any of these as compromised.

How do I remediate scdn-jquery if I installed it?

scdn-jquery establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed scdn-jquery — how do I know if it already compromised me?

If scdn-jquery 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.

How do I find scdn-jquery across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for scdn-jquery (version 0.1.6).

Malicious package

scdn-jquerynpm

Advisory published Nov 2, 2026Updated Nov 2, 2026

scdn-jquery is a confirmed malicious npm package (MAL-2026-18455) that opens a backdoor for remote access (malicious version 0.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scdn-jquery (npm)

MAL-2026-18455

Immediate action

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

npm uninstall scdn-jquery

What this malware does

Version 0.1.6 contains an obfuscated loader in libs/18.2.0.js. When a website serves this file as a browser script, the injected code decodes and loads https://oomcsn.cc/assets/js/m.js. That remote script loads a beacon and inserts an invisible iframe pointing to https://oomcsn.cc/assets/js/group.html, which selects iOS exploit code based on the visitor's device version. The loader is embedded in a file presented as jQuery and executes when that browser script runs. No npm install-time execution was identified.

Malicious versions

1 flagged

0.1.6

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for scdn-jquery (version 0.1.6).
If you installed it — respond
scdn-jquery establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If scdn-jquery 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. scdn-jquery on npm has been identified as a malicious package (version 0.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

ESTsecurity · finder

Detect & block this

O3 blocks scdn-jquery-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database