# MAL-2026-13652: Malicious code in sme-rko-finance-front-operations-widget-models (npm)


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

## What is MAL-2026-13652?

MAL-2026-13652 is a malicious package in sme-rko-finance-front-operations-widget-models, published on 8 Aug 2026. 

### Official description

On require of the package, `_platform.js` and `lib/telemetry.js` run a bootstrap that selects a platform-specific asset, fetches an opaque binary from one of three anonymous Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), writes it to a temp path with a randomized name, chmods it 0755 on POSIX, and spawns it detached via `/bin/sh -c "<path> &"` or `cmd.exe /c start`, with `.unref()` to survive the parent process. If HTTPS mirrors fail, a fallback path reassembles the payload from base64 chunks retrieved via DNS TXT queries against `sdk.dl.wel1.ru`, `ext.dl.wel1.ru`, `pkg.dl.wel1.ru`, and `net.dl.wel1.ru`. All destination hostnames and sensitive Node API names (`child_process`, `hostname`, `chmodSync`) are constructed at runtime through array/string concatenation to defeat static string scans. An `.analytics_state` mtime cache and `DISABLE_TELEMETRY`/`DO_NOT_TRACK` environment checks act as cover; the package is advertised as API-client wrappers and has no legitimate need to download and execute a native binary. The dropper logic is duplicated across `_platform.js` and the main `lib/telemetry.js` load path so the payload runs even if one entry point is removed.

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

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-13652 is a malicious package: sme-rko-finance-front-operations-widget-models (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-13652/ (Markdown: https://insights.sbomify.com/MAL-2026-13652/index.md)
```

## Sources

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

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