sme-foundation-frame-managernpm
sme-foundation-frame-manager is a confirmed malicious npm package (MAL-2026-12439) that executes malicious code on install (malicious version 20.7.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sme-foundation-frame-manager (npm)
What this malware does
On require/import of the package, index.js unconditionally loads runtime.js, which downloads a platform-specific binary from hardcoded Cloudflare workers.dev endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked base64 fallback resolved through *.well1.site. The binary is written to /tmp or %TEMP% under deceptive names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod 0755'd, and executed detached via /bin/sh or cmd.exe. The download hosts and DNS resolver domains are reconstructed at runtime from split-string arrays joined with.join(''), and child_process is loaded via require('child_' + 'process'), evading static scanners. No hash or signature verification is performed on the fetched binary.
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-foundation-frame-manager (version 20.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sme-foundation-frame-manager across your stack and pipelines.
If you installed it — respond
Remove sme-foundation-frame-manager 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-foundation-frame-manager 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-foundation-frame-manager 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-foundation-frame-manager-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.