Version 0.1.6 of the npm package scdn-jquery carried an obfuscated browser loader in libs/18.2.0.js that loaded a remote script from oomcsn.cc.
GitHub advisory GHSA-543q-wq5f-hmgh and OpenSSF record MAL-2026-18455 list scdn-jquery 0.1.6 as malicious code. npm removed the package, so the code was unavailable for inspection.
What happened
A version of scdn-jquery went up on npm on 26 October 2026 with a hidden loader. The advisories describe these actions:
- Version 0.1.6 adds an obfuscated loader in
libs/18.2.0.js. - When a website serves that file to a browser, the loader fetches
https://oomcsn.cc/assets/js/m.js. - The remote script inserts a hidden iframe that points to
https://oomcsn.cc/assets/js/group.html. - That page selects iOS exploit code by the visitor's device version.
GitHub states that it found no npm install-time execution. ESTsecurity and Amazon Inspector are the finders in the OpenSSF record. GitHub published its advisory on 2 November 2026. npm replaced the package with a security holder on 3 November 2026.
Affected versions
scdn-jquery0.1.6, published2026-10-26T13:10:16.316Z(GitHub lists this version only).- OSV record MAL-2026-18455 lists 0.1.6 and the range
0.*. - npm also lists versions 0.1.0 to 0.1.5 (24 October 2026) and 0.1.7 (1 November 2026). No source says if they are clean.
Indicators of compromise
- Domain:
oomcsn.cc. - URL:
https://oomcsn.cc/assets/js/m.js. - URL:
https://oomcsn.cc/assets/js/group.html. - File:
libs/18.2.0.js. - SHA-256 of
libs/18.2.0.js(OpenSSF):91f747d4c8751b73cc65ee69ba86d8a30310b1b1bef5ffebc3682efb4b238c86.
How to check
List the package in your project:
npm ls scdn-jquery
Search your source and built site for the domain:
grep -rn "oomcsn.cc" .
What to do now
- If you find
scdn-jquery, remove it frompackage.jsonand the lockfile. - Remove every script tag that loads
libs/18.2.0.jsfrom this package. - Block
oomcsn.ccat your DNS or proxy. - If the package ran on a computer, rotate the secrets on that computer from a different computer, as the GitHub advisory directs.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `scdn-jquery` 0.1.6. This version is too new or changed in a way Vigilance must check first. The last safe version is 0.1.5. Install that version.
In the owner report
Bad update
scdn-jquery 0.1.6
This update now downloads from the internet and runs other programs. The version before it did not.
- Ask the AI tool to swap scdn-jquery to 0.1.5. That is the last safe version.
Frequently asked questions
Is scdn-jquery malware?
GitHub advisory GHSA-543q-wq5f-hmgh and OpenSSF record MAL-2026-18455 list version 0.1.6 as malicious code. npm removed the package on 3 November 2026.
Does installing scdn-jquery run the malware?
GitHub states that it found no npm install-time execution. The advisories say the code runs when a website serves libs/18.2.0.js to a browser.