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

sme-rko-finance-front-operations-taxnpm

sme-rko-finance-front-operations-tax is a confirmed malicious npm package (MAL-2026-13649) 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-operations-tax (npm)

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

What this malware does

On require, index.js loads platform.js and lib/telemetry.js, which download a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, cf103-070, cf102-baf) with a DNS TXT-record fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or Windows Temp under disguised names (e.g.,.cache<hex>, dotnet_diag_<hex>.exe), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and sensitive API names (child_process, chmodSync) are reassembled at runtime from split string arrays to defeat static analysis. The package's stated purpose (finance/tax operations frontend) has no legitimate need to fetch and execute an opaque native binary from non-publisher infrastructure.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

ede42a446ab3685943424af5a5411fb93bf5961c83ccf6ce02b35b8d835c60aa

Detection & response playbook

Malicious package
  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-operations-tax (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-operations-tax across your stack and pipelines.

  2. If you installed it — respond

    Remove sme-rko-finance-front-operations-tax 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.

  3. Did it already run?

    If sme-rko-finance-front-operations-tax 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-operations-tax 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-operations-tax 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-017166

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sme-rko-finance-front-operations-tax-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

sme-rko-finance-front-operations-tax (npm) malicious package — MAL-2026-13649 | O3 Security