Which versions of express-route-engine are malicious?

The following npm versions of express-route-engine are flagged malicious: 3.6.3. Treat any of these as compromised.

How do I remediate express-route-engine if I installed it?

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

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

Yes — express-route-engine is associated with the IN-MAL-2026-018429 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-route-engine 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-route-engine (version 3.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-route-engine across your stack and pipelines.

Malicious package

express-route-enginenpm

express-route-engine is a confirmed malicious npm package (MAL-2026-14307) that executes malicious code on install (malicious version 3.6.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-route-engine (npm)

MAL-2026-14307

Immediate action

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

npm uninstall express-route-engine

What this malware does

On require/import, index.js immediately invokes an initializer that HTTP-GETs a JSON document from https://api.jsonbin.io/v3/b/6a4f5816f5f4af5e29762c92, extracts the record.cerookie field, and executes its contents as JavaScript via new (Function.constructor)('require',...)(require). The evaluated code runs with full Node.js privileges and access to require, and the payload is hosted on a third-party mutable JSON store controlled by the package author, so the executed code can change at any time without republishing. The file is cover-labeled as normalize-path (ES6 safe version) and contains an unused normalizePath helper and a Safe request helper comment to obscure the loader; the Function constructor is reached indirectly via Function.constructor and the payload field is named cerookie to reduce recognizability. The stated purpose (an Express route engine) has no legitimate need to fetch and evaluate remote code on load.

Malicious versions

1 flagged

3.6.3

Indicators of compromise (SHA-256)

8f54041362d71f16d1ee889c3992558cec28371030eaca4a3962ac0e9e3ec55d

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

Campaign

IN-MAL-2026-018429

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks express-route-engine-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