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

bigops-figma-to-htmlnpm

bigops-figma-to-html is a confirmed malicious npm package (MAL-2026-12166) that steals credentials and exfiltrates sensitive data (malicious version 35.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-figma-to-html (npm)

MAL-2026-12166
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bigops-figma-to-html

What this malware does

On require, index.js unconditionally loads bootstrap.js, which selects a platform-specific endpoint, fetches an opaque binary from author-controlled Cloudflare Workers subdomains (oob-worker.cf*.workers.dev) with a DNS-TXT chunked fallback over *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru), writes it to /var/tmp/.cache<hex> on POSIX or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached and unref'd via /bin/sh -c or cmd. Destination hostnames are constructed at runtime by joining split-string fragments (e.g. ["oob-wo","rker.cf103-070.worke","rs.de","v"].join("")) to hide them from static scanners. The DNS-TXT fallback retrieves a chunk count from c.<domain> and reassembles base64 chunks from N.<domain>, providing a covert delivery channel that bypasses HTTPS egress filtering. No hash or signature verification is performed; filenames impersonate dotnet diagnostics artifacts; opt-out is only via undocumented environment variables.

Malicious versions

1 flagged
35.5.5

Indicators of compromise (SHA-256)

c9d43dbcd2d43f28af8266fac2d7e08a782dfbaaac1d02375438095a8001b24e

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-figma-to-html (version 35.5.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-figma-to-html across your stack and pipelines.

  2. If you installed it — respond

    bigops-figma-to-html is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If bigops-figma-to-html 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 bigops-figma-to-html 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. bigops-figma-to-html on npm has been identified as a malicious package (version 35.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014416

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bigops-figma-to-html-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bigops-figma-to-html (npm) malicious package — MAL-2026-12166 | O3 Security