Which versions of enquriers are malicious?

The following npm versions of enquriers are flagged malicious: 2.4.1, 2.4.2. Treat any of these as compromised.

How do I remediate enquriers if I installed it?

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

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

Yes — enquriers is associated with the GHSA-c8vc-qqjp-wg87, IN-MAL-2026-008783, IN-MAL-2026-008782 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 enquriers 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 enquriers (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging enquriers across your stack and pipelines.

Malicious package

enquriersnpm

Malicious code in enquriers (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5384

Immediate action

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

npm uninstall enquriers

What this malware does

Package name 'enquriers' closely resembles the widely-used 'enquirer' package (transposed/added characters), suggesting potential name-confusion risk. No malicious payload, exfiltration, dropper, credential access, or install-time code execution was identified in the package contents. Without a concrete installer-harm mechanism, name-similarity alone is a subjective signal that warrants human review rather than automated blocking.

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

2.4.12.4.2

Indicators of compromise (SHA-256)

17ff0053c1f18c2d4e2e555119e16463f85cfb7f0c564d64d222a80a84763639

7c7f041bb6800c0c765683543b18f204299e64265c3d9124c54f7f0169b53348

f19572423b435424694a0531bd7fc54057b1cea5bb928315fb5286dc767af85d

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

Campaign

GHSA-c8vc-qqjp-wg87IN-MAL-2026-008783IN-MAL-2026-008782

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks enquriers-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