Which versions of zyncmap are malicious?

The following npm versions of zyncmap are flagged malicious: 0.0.0, 0.0.1. Treat any of these as compromised.

How do I remediate zyncmap if I installed it?

zyncmap establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed zyncmap — how do I know if it already compromised me?

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

Is zyncmap part of a known attack campaign?

Yes — zyncmap is associated with the IN-MAL-2026-007854, IN-MAL-2026-007855 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find zyncmap across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zyncmap (2 malicious versions).

Malicious package

zyncmapnpm

Advisory published Jul 1, 2026Updated Jul 1, 2026

zyncmap is a confirmed malicious npm package (MAL-2026-6708) that opens a backdoor for remote access (malicious versions 0.0.0, 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zyncmap (npm)

MAL-2026-6708

Immediate action

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

npm uninstall zyncmap

What this malware does

[email protected] advertises itself as an SVG sanitization/minification utility, but index.js exports an undocumented function getPlugin() that, when invoked, performs an HTTP GET against the anonymous paste host https://www.jsonkeeper.com/b/3P9BF and passes the response's model string field directly to eval(). Content at that paste URL is attacker-mutable, so any consumer that calls the exported getPlugin() executes arbitrary attacker-controlled JavaScript in the installer's Node.js process. The README and ~80% of index.js implement plausible SVG helpers as cover; the remote-fetch+eval export and a misleading bearrtoken: "logo" header are appended separately and not mentioned in package documentation. This is a backdoor: a hidden code path giving the publisher persistent remote code execution against any consumer who reaches the export.

Malicious versions

2 flagged

0.0.00.0.1

Indicators of compromise (SHA-256)

251e5b6920fb8a9fdb59aba6c1b162ddd27f0b226c979e62fb43845fc0f5d9ae

3a65a1106fa2bab6eb0b5982b289665b4b96a6ad86769a867f6e62fb73663f77

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for zyncmap (2 malicious versions).
If you installed it — respond
zyncmap establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If zyncmap 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. zyncmap on npm has been identified as a malicious package (versions 0.0.0, 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007854IN-MAL-2026-007855

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zyncmap-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database