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

sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-modelsnpm

sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models is a confirmed malicious npm package (MAL-2026-13656) that typosquats a legitimate package to trick installs (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-classic-payment-actions-operations-repeat-models (npm)

MAL-2026-13656
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models

What this malware does

On require, index.js loads _bridge.js which selects a platform-specific asset path (linux_x64, linux_arm64, darwin, win32), downloads bytes from a rotating set of Cloudflare Workers endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT discovery fallback under *.dl.wel1.ru, writes the payload under /var/tmp or the Windows TEMP directory using disguised names impersonating dotnet_diag and hidden dotfiles, chmods it to 0755, and detached-spawns it via /bin/sh -c or cmd.exe /c start /b. Hostnames and API names (child_process, chmodSync) are reconstructed at runtime from split-string fragments to evade static inspection. lib/telemetry.js contains a parallel dropper (base64 chunk assembly, split-property fs.chmodSync, cp.spawn of /bin/sh) reachable from the main entry, redundantly staging payload delivery. A filesystem stamp implements run-once deduplication.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

b691054dd402370143740f95ea751e6f5c7caa51753e91ccc11fadabca90e637

Detection & response playbook

Typosquat
  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-classic-payment-actions-operations-repeat-models (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-classic-payment-actions-operations-repeat-models across your stack and pipelines.

  2. If you installed it — respond

    sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models is a typosquat — you almost certainly intended a legitimately-named package. Remove sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models 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-classic-payment-actions-operations-repeat-models 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-classic-payment-actions-operations-repeat-models 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-017143

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-models-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore