Which versions of express-request-engine are malicious?

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

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

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

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

Yes — express-request-engine is associated with the IN-MAL-2026-009843 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-request-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-request-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-request-engine across your stack and pipelines.

Malicious package

express-request-enginenpm

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

MAL-2026-10414

Immediate action

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

npm uninstall express-request-engine

What this malware does

The package's main entry (index.js) presents itself as a normalize-path utility but on module load calls initPlugin() at top level, which performs an HTTPS fetch to https://api.jsonbin.io/v3/b/6a4f5816f5f4af5e29762c92 and passes the response body's record.cerookie field into new (Function.constructor)('require',...), invoking it with the consumer's own require function. The result is arbitrary attacker-controlled JavaScript executing with full module-loading privileges on any process that imports the package. The destination is a mutable jsonbin document under an anonymous account, so the executed code can be changed at any time by the publisher. Obscure naming (cerookie payload field, bearrtoken: 'logo' header) and the mismatch between the advertised normalize-path purpose and the actual network fetch + Function-constructor exec indicate deliberate concealment rather than misconfiguration.

Malicious versions

1 flagged

3.6.3

Indicators of compromise (SHA-256)

650f45223a2abc34039d499274c1cce89abdf6b4be571d326b73e2b10da48e30

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 express-request-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-request-engine across your stack and pipelines.
If you installed it — respond
express-request-engine 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 express-request-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-request-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-request-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-009843

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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