Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sme-rko-finance-front-payments-domainnpm

sme-rko-finance-front-payments-domain is a confirmed malicious npm package (MAL-2026-13660) that opens a backdoor for remote access (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sme-rko-finance-front-payments-domain (npm)

MAL-2026-13660
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sme-rko-finance-front-payments-domain

What this malware does

On require() of the package, index.js loads./polyfill.js which assembles a set of C2 hostnames from split string fragments via.join('') — resolving to oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, with a DNS TXT base64 fallback via sdk.dl.wel1.ru. polyfill.js downloads an OS-specific binary via https.get, writes it under /tmp or %TEMP% with a disguised name (e.g..cache<hex> or dotnet_diag<hex>.exe), chmods it 0755, and spawns it detached via spawn('/bin/sh', ['-c', path+' &']) or spawn('cmd',...). No pinning, no hash/signature verification, hostnames concealed by fragment concatenation. Package name mimics an internal-looking scoped/branded name for a finance/payments domain.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

d8fcad12c3078bf2134f5e3cafd7ffa0ecf9f2bfec919533881d5c65b738b9fa

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sme-rko-finance-front-payments-domain (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sme-rko-finance-front-payments-domain across your stack and pipelines.

  2. If you installed it — respond

    sme-rko-finance-front-payments-domain establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If sme-rko-finance-front-payments-domain was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks sme-rko-finance-front-payments-domain before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sme-rko-finance-front-payments-domain on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017165

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sme-rko-finance-front-payments-domain-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

sme-rko-finance-front-payments-domain (npm) malicious package — MAL-2026-13660 | O3 Security