Which versions of express-deflect are malicious?

The following npm versions of express-deflect are flagged malicious: 1.6.10, 1.6.12. Treat any of these as compromised.

How do I remediate express-deflect if I installed it?

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

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

Yes — express-deflect is associated with the GHSA-968w-6262-r9f5, IN-MAL-2026-008900, IN-MAL-2026-009554 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-deflect 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-deflect (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-deflect across your stack and pipelines.

Malicious package

express-deflectnpm

express-deflect is a confirmed malicious npm package (MAL-2026-6908) that executes malicious code on install (malicious versions 1.6.10, 1.6.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-deflect (npm)

MAL-2026-6908

Immediate action

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

npm uninstall express-deflect

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

2 flagged

1.6.101.6.12

Indicators of compromise (SHA-256)

bf92073506c665a47e6b052bcece26d956734c327024d46aba40b6a2cc2712ab

284d3f4c5f55f69391b1172ba9d2c714e3ae358a2c92a501049a1495547e1588

c15ebbaf9066f13850802f5722d31a901e4df40148cc27653b366ca0974a900b

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

Campaign

GHSA-968w-6262-r9f5IN-MAL-2026-008900IN-MAL-2026-009554

References

Credits

Amazon Inspector · finder

Detect & block this

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