Which versions of react-markdown-canvas are malicious?

The following npm versions of react-markdown-canvas are flagged malicious: 1001.0.0, 1005.0.0. Treat any of these as compromised.

How do I remediate react-markdown-canvas if I installed it?

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.

I already installed react-markdown-canvas — how do I know if it already compromised me?

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.

How do I find react-markdown-canvas across my projects, lockfiles, and CI pipelines?

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.

Malicious package

react-markdown-canvasnpm

react-markdown-canvas is a confirmed malicious npm package (MAL-2026-1040) that steals credentials and exfiltrates sensitive data (malicious versions 1001.0.0, 1005.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-markdown-canvas (npm)

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

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.
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.
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.
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

app.safedep.io

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database