Which versions of routing-controls are malicious?

The following npm versions of routing-controls are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate routing-controls if I installed it?

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

If routing-controls 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.

Is routing-controls part of a known attack campaign?

Yes — routing-controls is associated with the GHSA-jmhh-mvpj-27qq, IN-MAL-2026-008943 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 routing-controls 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 routing-controls (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging routing-controls across your stack and pipelines.

Malicious package

routing-controlsnpm

routing-controls is a confirmed malicious npm package (MAL-2026-5635) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in routing-controls (npm)

MAL-2026-5635

Immediate action

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

npm uninstall routing-controls

What this malware does

Package name routing-controls is a one-edit variant of the popular routing-controllers package (~1M weekly downloads), and the README and source are a near-verbatim clone. Inside build/cjs/RoutingControllers.js lines 84-88, the executeAction method contains a non-standard code path that fires on every POST action: it resolves ./util/lib.min.js, deletes the entry from require.cache, and re-requires the file. In version 1.0.1 the target file build/cjs/util/lib.min.js (and its esm2015 sibling) is a 100-byte stub containing only console.log('[routing-controls] POST route invoked at ' + new Date().toISOString());, so no actively harmful behavior fires today. However, the misleading .min.js suffix on a stub file paired with a cache-busting reload on every POST is the structural shape of a hot-swappable trigger — a follow-up version could replace lib.min.js with arbitrary code that runs on every POST request in any application using this library. The current version exhibits no exfiltration, no remote fetch, no install-time execution, and no credential access; the harm is latent and depends on a future republication.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

095efa733141879758b3a97acff66255dd2bc05143649513ab18b6597bf2dedb

bcd98c45663ebd03d8f553589ef12e33bae9518be150ef7dca94881592a1827d

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 routing-controls (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging routing-controls across your stack and pipelines.
If you installed it — respond
routing-controls 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 routing-controls 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 routing-controls 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. routing-controls on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jmhh-mvpj-27qqIN-MAL-2026-008943

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks routing-controls-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