Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@ornikar/typed-css-modules-loadernpm

@ornikar/typed-css-modules-loader is a confirmed malicious npm package (MAL-2026-11779) that steals credentials and exfiltrates sensitive data (malicious versions 0.8.2, 0.8.3, 0.8.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ornikar/typed-css-modules-loader (npm)

MAL-2026-11779
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ornikar/typed-css-modules-loader

What this malware does

npm/@ornikar/typed-css-modules-loader is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook ("preinstall": "node setup.mjs") that runs on a bare npm install, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations.

@ornikar/[email protected] is presented as a webpack loader for typed-css-modules but on install runs an attacker-controlled dropper. The package.json preinstall script invokes setup.mjs, which downloads the Bun runtime archive from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/, extracts and chmods the Bun binary, and uses it to execute a sibling file math_init.js via execFileSync(bunPath, [join(D, 'math_init.js')], {stdio:'inherit', cwd:D}). math_init.js is a single-line ~700KB Bun-compiled CJS bundle beginning with // @bun @bun-cjs followed by a large hex opcode/data table (const n7gIxM=[0x0,0x1,0x8,0xff,"length",...]) with no plain-text identifiers, URLs, or function names; setup.mjs itself is obfuscated with hex-mangled identifiers (_0x488df8 style) despite implementing only a download-and-exec flow. The Bun runtime executes the bundle outside Node-based scanners and outside npm's script visibility. The payload's name (math_init) has no relation to the advertised webpack-loader purpose. The package also shows a scope/author mismatch: name is under the @ornikar org scope, but repository, homepage, bugs, and author (Oleg Stepura) all point at the unrelated olegstepura/typed-css-modules-loader upstream, consistent with a scope-squat wrapping a dropper around an existing package identity.

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

11 flagged
0.8.20.8.30.8.40.8.50.8.60.8.70.8.80.8.90.8.100.8.110.8.12

Indicators of compromise (SHA-256)

54374f348631a22fd654fb8224940b3cfbf42aad18c3e865d0d316f0bfc5292d
ae5f9f7c6302128d9617caa6ec4c129465f1257716c2659f2a961ae8cbbd379b
f5f2a048ed17ca7dabaae6362ebad9bea5d2da2c9119ab90660f78d439328399
44f6eda371f3166750e13c4870d625692131c32843f06dbd0a38363ba807c877
62a24e1bedf9074b710fbd62d8ac67f1d3a7a453634b7dce05e2d7dc36bdf483
6f97bb3119dcc22003107335f66c388f2de3461fcf10845819a2afe36d9ba459
b0261df3b35b680908af12e0fca16c70faa0f58f91cf88f79033d0f5af6052e5
c388d3b4096854d4ccd73c0c10e5e6fc84aeec3d5f2dcd0eaa503107356c874e
e5ff223c2d8e7cae2e299dff905d523c3d922303b84887ec5594d35aaee5f0da
06e9fcccb0ddf781c4727d02f57ba56183769ca22777b4c4f87ed88f2ff6d48d
6e400c2820957cd992fd32c5561d9287a57b06a43326b2d462ae1f885f4ccb60
ba019ba09cf2f7254d72fecaa28d1e77f9c22f7c569e805053691a75ed962a9e

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ornikar/typed-css-modules-loader (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ornikar/typed-css-modules-loader across your stack and pipelines.

  2. If you installed it — respond

    @ornikar/typed-css-modules-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @ornikar/typed-css-modules-loader 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.

  4. How O3 protects you

    O3 blocks @ornikar/typed-css-modules-loader 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. @ornikar/typed-css-modules-loader on npm has been identified as a malicious package (versions 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.8.9, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f5fc-5jm9-g69xIN-MAL-2026-011376IN-MAL-2026-011756IN-MAL-2026-011544IN-MAL-2026-011870IN-MAL-2026-011871IN-MAL-2026-011869IN-MAL-2026-011752IN-MAL-2026-011754IN-MAL-2026-011872IN-MAL-2026-011755IN-MAL-2026-011753

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @ornikar/typed-css-modules-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@ornikar/typed-css-modules-loader (npm) malicious package — MAL-2026-11779 | O3 Security