Which versions of react-leaflet-marker-layer are malicious?

The following npm versions of react-leaflet-marker-layer are flagged malicious: 0.1.5. Treat any of these as compromised.

How do I remediate react-leaflet-marker-layer if I installed it?

react-leaflet-marker-layer 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-leaflet-marker-layer — how do I know if it already compromised me?

If react-leaflet-marker-layer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find react-leaflet-marker-layer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-leaflet-marker-layer (version 0.1.5).

Malicious package

react-leaflet-marker-layernpm

Advisory published Mar 26, 2026Updated Mar 31, 2026

react-leaflet-marker-layer is a confirmed malicious npm package (MAL-2026-2215) that steals credentials and exfiltrates sensitive data (malicious version 0.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-leaflet-marker-layer (npm)

MAL-2026-2215

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-leaflet-marker-layer

What this malware does

The package react-leaflet-marker-layer was found to contain malicious code.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

1 flagged

0.1.5

Indicators of compromise (SHA-256)

306d70c46c0fb0ef8d41b5f8c730d785a321c0576641ef05de403e0276b1e0e8

7b37a04b363c4392e401d85320c748dab98c13ff46c74624f21aaa70091b8ae6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for react-leaflet-marker-layer (version 0.1.5).
If you installed it — respond
react-leaflet-marker-layer 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-leaflet-marker-layer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. react-leaflet-marker-layer on npm has been identified as a malicious package (version 0.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-leaflet-marker-layer-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