Which versions of swagger-express-routes are malicious?

The following npm versions of swagger-express-routes are flagged malicious: 1.0.1. Treat any of these as compromised.

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

Remove swagger-express-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 swagger-express-routes — how do I know if it already compromised me?

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

Yes — swagger-express-routes is associated with the GHSA-49jc-pgvv-m729, IN-MAL-2026-006084, IN-MAL-2026-006085 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 swagger-express-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 swagger-express-routes (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 swagger-express-routes across your stack and pipelines.

Malicious package

swagger-express-routesnpm

swagger-express-routes is a confirmed malicious npm package (MAL-2026-5636) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in swagger-express-routes (npm)

MAL-2026-5636

Immediate action

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

npm uninstall swagger-express-routes

What this malware does

On require('swagger-express-routes'), the package's main entry transitively loads src/utils/lib.min.js through src/connector/index.js (line 1: require('../utils/lib.min.js')). lib.min.js stashes Node's require and module onto global (global['r']=require), then uses a permutation-cipher routine (YWG) to deobfuscate a string blob, passes it to the Function constructor, and immediately invokes the resulting function. This is dynamic execution of an opaque payload reconstructed at runtime — the canonical anti-analysis pattern of an embedded supply-chain payload. Re-exposing require via a global alias lets the deobfuscated code pull in child_process, http, fs, etc. without those references being statically visible. None of this is documented in the README, and there is no legitimate reason for a small Express/OpenAPI helper to ship a permutation-deobfuscated Function-eval blob on its import path. Any consumer of this package executes the payload at require time.

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)

2e0b96b2f07780758dae22385ae7f681656ae4a941f299d9b37788362fe56e4f

342bf1e361c6684c276c1afc618d78d82268e93898daddaef74873a49c6111b2

ed21bdad615599dfaaa86f7d89d8b5c713c51be0cf33981e7125b1f38bf88648

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 swagger-express-routes (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 swagger-express-routes across your stack and pipelines.
If you installed it — respond
Remove swagger-express-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 swagger-express-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 swagger-express-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. swagger-express-routes 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-49jc-pgvv-m729IN-MAL-2026-006084IN-MAL-2026-006085

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks swagger-express-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

Explore

All malware advisories How O3 detects malware Vulnerability database