Which versions of router-processor are malicious?

The following npm versions of router-processor are flagged malicious: 1.5.2. Treat any of these as compromised.

How do I remediate router-processor if I installed it?

router-processor 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 router-processor — how do I know if it already compromised me?

If router-processor 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 router-processor part of a known attack campaign?

Yes — router-processor is associated with the IN-MAL-2026-010263 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 router-processor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for router-processor (version 1.5.2).

Malicious package

router-processornpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

router-processor is a confirmed malicious npm package (MAL-2026-10453) that steals credentials and exfiltrates sensitive data (malicious version 1.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in router-processor (npm)

MAL-2026-10453

Immediate action

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

npm uninstall router-processor

What this malware does

[email protected] exposes a getPlugin function that assembles the URL https://svganchordev.net/icons/107 from split constants (protocol, separator, domain, path), fetches a JSON response, and passes the credits field to new Function(...) which is then invoked with a context object exposing require, process, Buffer, and other Node.js internals. This executes arbitrary attacker-controlled JavaScript with full Node privileges in the caller's process. The package declares dependencies on DPAPI bindings (Windows credential decryption), better-sqlite3, and node-machine-id, which are consistent with an infostealer loader capable of decrypting browser credential stores. The package's identity is inconsistent: package.json describes a router processor while the README advertises a Polymarket SDK, and neither matches the observed behavior of fetching remote code from an SVG-themed cover-story domain. The URL split-construction and the misleading credits/getPlugin naming are deliberate evasion of casual review.

Malicious versions

1 flagged

1.5.2

Indicators of compromise (SHA-256)

d15d816c739a85908172d716580a6e4cb0655fe7b2fe35293b218db80f9b2625

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for router-processor (version 1.5.2).
If you installed it — respond
router-processor 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 router-processor 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. router-processor on npm has been identified as a malicious package (version 1.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010263

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks router-processor-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