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

react-markdown-canvasnpm

Malicious code in react-markdown-canvas (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1040
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-markdown-canvas

What this malware does

Malicious package due to data exfiltration via Discord webhook on install. Collects IP, hostname, and date without consent.

The package react-markdown-canvas was found to contain malicious code.

The OpenSSF Package Analysis project identified 'react-markdown-canvas' @ 1001.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged
1001.0.01005.0.0

Indicators of compromise (SHA-256)

833c2865c0a6f984f9af493aa02b5ec03e8a63f037c298a46ae54bb1d88d3a1a
eebf5582865e2a81a8d7e00e967725e011a5317109ff891b5b281df547349c63
4123db6526d8c37f99fa33e2524edc97922efef6b1605dc0a8acdbf41e76cc77

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 react-markdown-canvas (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-markdown-canvas across your stack and pipelines.

  2. If you installed it — respond

    react-markdown-canvas 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 react-markdown-canvas 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 react-markdown-canvas 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. react-markdown-canvas on npm has been identified as a malicious package (versions 1001.0.0, 1005.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • SafeDep · finder

Detect & block this

O3 blocks react-markdown-canvas-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

react-markdown-canvas (npm) malicious package — MAL-2026-1040 | O3 Security