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


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

## What is MAL-2026-13653?

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

### Official description

index.js unconditionally loads _runtime.js on require. _runtime.js detects the host OS and architecture, then downloads an opaque platform-matched binary over HTTPS from hardcoded Cloudflare workers.dev subdomains (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev). If HTTPS retrieval fails, it falls back to a DNS-TXT covert channel under *.dl.wel1.ru, requesting a chunk-count TXT record at c.<domain> and then reassembling base64-encoded payload chunks from N.<domain> TXT queries. The reassembled bytes are written to /var/tmp or %TEMP% under a disguised filename (.cache_<rand> or dotnet_diag_<rand>.exe mimicking a.NET diagnostic tool), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Both the CDN hostnames and the fallback resolver domains are constructed by Array.join of split fragments to evade string scanning. The delivered binary is unpinned, unverified, opaque, and served from anonymous edge-worker infrastructure and a.ru DNS channel unrelated to any legitimate publisher of a finance/payment-registers package.

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

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

## Sources

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

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