sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-implnpm
sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-impl is a confirmed malicious npm package (MAL-2026-13655) that executes malicious code on install (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-impl (npm)
What this malware does
On require() of the package, index.js loads _bootstrap.js which selects a payload path based on process.platform/arch (linux_x64, linux_arm64, darwin, win32), downloads an executable over HTTPS from one of several Cloudflare Workers subdomains whose hostnames are assembled at runtime via array-join obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64 chunked fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name, chmod 755, and spawned detached via /bin/sh -c or cmd.exe. The package.json describes the module as "API client wrappers" for an internal payments module, but the on-load behavior is unrelated OS-branched remote code execution. Hostname obfuscation via array-join and a DNS-TXT fallback resolver are deliberate evasion of static string scanners.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-impl (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-impl across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-impl from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-impl 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.
How O3 protects you
O3 blocks sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-impl 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sme-rko-finance-front-payments-classic-payment-actions-operations-repeat-impl-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.