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

sme-rko-finance-front-operations-feed-modelsnpm

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

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

What this malware does

index.js unconditionally requires./runtime on package load. runtime.js selects a platform-specific endpoint, downloads a binary over HTTPS from one of four string-split *.workers.dev hosts (e.g. oob-worker.cf103-070.workers.dev), with a DNS TXT chunked-base64 fallback to sdk.dl.wel1.ru, writes the payload to /tmp or %TEMP% under a decoy name (.cache<hex> or dotnet_diag<hex>.exe), chmods it 0755, and detach-spawns it via /bin/sh -c or cmd.exe. Network destinations are assembled at runtime by joining fragmented string arrays to evade static analysis, filenames impersonate dotnet diagnostics, and execution is rate-limited via a stamp file in /tmp. The fetched bytes are attacker-controlled opaque native executables unrelated to the package's stated purpose.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

13827ca573a120c853faeb2b9ccfe34d627e098b5917cee97d5eecd45b81e9dc

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-operations-feed-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-operations-feed-models across your stack and pipelines.

  2. If you installed it — respond

    sme-rko-finance-front-operations-feed-models is a typosquat — you almost certainly intended a legitimately-named package. Remove sme-rko-finance-front-operations-feed-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-operations-feed-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-operations-feed-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-operations-feed-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-017138

References

Credits

  • Amazon Inspector · finder

Detect & block this

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