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


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

## What is MAL-2026-13641?

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

### Official description

On require of the package, index.js side-effect loads _polyfill.js and lib/telemetry.js, both of which act as native-binary droppers. Hostnames and privileged API names are assembled via array.join('') to evade static scans (e.g. require("child_" + "process"), _MIRRORS built from ["oob-worker.cf102-baf.worke","rs.d","ev"].join('')). The code downloads a platform-specific binary via https.get from oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf101-adf.workers.dev, with a DNS TXT fallback under *.dl.wel1.ru that base64-reassembles the payload. The fetched bytes are written to /var/tmp/.cache_<rand> or %TEMP%\dotnet_diag_<rand>.exe (masquerading as a dotnet diagnostic file), chmod 0755'd, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or cmd.exe /c start /b. lib/telemetry.js contains a parallel dropper path (base64 chunk assembly, chmodSync to 0755, cp.spawn('/bin/sh',...)) so execution occurs even if _polyfill.js is removed. The declared 'core infrastructure utilities / telemetry' purpose does not match downloading and executing opaque native binaries from anonymous Cloudflare Workers subdomains.

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

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

## Sources

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

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