Which versions of express-groups-routes are malicious?

The following npm versions of express-groups-routes are flagged malicious: 0.0.1-security, 3.7.5, 3.7.7. Treat any of these as compromised.

How do I remediate express-groups-routes if I installed it?

Remove express-groups-routes from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed express-groups-routes — how do I know if it already compromised me?

If express-groups-routes 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 express-groups-routes part of a known attack campaign?

Yes — express-groups-routes is associated with the GHSA-v866-jcq6-8pmv, RLMA-2026-01305 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 express-groups-routes 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 express-groups-routes (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-groups-routes across your stack and pipelines.

Malicious package

express-groups-routesnpm

Malicious code in express-groups-routes (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-722

Immediate action

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

npm uninstall express-groups-routes

What this malware does

The package express-groups-routes was found to contain malicious code.

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

3 flagged

0.0.1-security3.7.53.7.7

Indicators of compromise (SHA-256)

c8c5983f3ca1d455b0aee9018074650c3aed0db620fc55a8f34e49b376017433

5d54e03ffa96877bc24a447c0a77e5c096894fd82176e5705d62713eb5f20f10

3b200220596c79eb3bed0968b14ecb19460544411a842c5d8f4afa8f9155fc1a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for express-groups-routes (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-groups-routes across your stack and pipelines.
If you installed it — respond
Remove express-groups-routes from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If express-groups-routes 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 express-groups-routes 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. express-groups-routes on npm has been identified as a malicious package (versions 0.0.1-security, 3.7.5, 3.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v866-jcq6-8pmvRLMA-2026-01305

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks express-groups-routes-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring