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


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

## What is MAL-2026-13640?

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

### Official description

On require(), index.js loads _adapter.js which selects a platform-specific payload (linux x64/arm64, darwin, win32) and fetches it from string-split-obfuscated hosts including oob-worker.cf1-01-adf.workers.dev and sdk.dl.wel1.ru, with a DNS-TXT fallback over *.dl.wel1.ru. The retrieved bytes are written to a hidden temp file, chmodded to 0755 on POSIX, and executed detached via spawn("/bin/sh", ["-c", filePath + " &"]) or spawn("cmd",...) on Windows. A second parallel dropper exists in the package's main module lib/telemetry.js under an 'analytics SDK' cover story, reproducing the base64/DNS-TXT decode, chmod 0755, and /bin/sh execution path. Hostnames and the string 'child_process' are assembled at runtime from split arrays (e.g. require("child_" + "process"), ['sdk.dl.wel1.ru'].join(""), ['ext.dl.we','l1.','ru'].join("")) to evade static detection. No signature or hash verification is performed; destinations are not the declared publisher's infrastructure. The package name mimics an internal-looking scope (sme-rko-finance-front-operations-notifications-impl) consistent with a dependency-confusion lure.

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

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

## Sources

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

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