# MAL-2026-13634: Malicious code in sme-rko-finance-front-operations-domain (npm)


- **Type:** Malicious package
- **Package:** `sme-rko-finance-front-operations-domain` (npm)
- **Published:** 8 Aug 2026

## What is MAL-2026-13634?

MAL-2026-13634 is a malicious package in sme-rko-finance-front-operations-domain, published on 8 Aug 2026. 

### Official description

On require of the package, index.js loads _shim.js which self-executes an async initializer that assembles platform-specific hostnames from split-string arrays (e.g. ["oob-worker.cf102-b","af.w","or","kers.","de","v"].join("") and ["pkg.dl.wel1.r","u"].join("")) targeting oob-worker.cf102-baf.workers.dev and sdk/ext/pkg/net.dl.wel1.ru, downloads a native binary over HTTPS, writes it to /tmp or %TEMP% under disguised names (.cache_<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. A DNS-TXT fallback channel (dns.resolveTxt on c.<domain>, 0.<domain>, 1.<domain>,...) reassembles and base64-decodes a payload when HTTPS retrieval fails, bypassing HTTP egress controls. lib/telemetry.js, loaded from index.js and presented as an observability/Sentry-like SDK, contains the same base64-materialize + chmodSync + child_process.spawn("/bin/sh",...) dropper primitives, providing a duplicate execution path. child_process, chmodSync, and endpoint hostnames are reconstructed at runtime from concatenated fragments to evade static scanners. No integrity check or pinned publisher-owned source; the fetched bytes are opaque and unverifiable.

## What should I do about MAL-2026-13634?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13634 is a malicious package: sme-rko-finance-front-operations-domain (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13634/ (Markdown: https://insights.sbomify.com/MAL-2026-13634/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13634

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13634/
Summaries are generated and may contain mistakes; the official description above is the record.