swagger-express-routes

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. ## Source: ghsa-malware (2e0b96b2f07780758dae22385ae7f681656ae4a941f299d9b37788362fe56e4f) 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.