Which versions of @carvana.authentication-flows/shared are malicious?

The following npm versions of @carvana.authentication-flows/shared are flagged malicious: 19.2.1. Treat any of these as compromised.

How do I remediate @carvana.authentication-flows/shared if I installed it?

@carvana.authentication-flows/shared 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 @carvana.authentication-flows/shared — how do I know if it already compromised me?

If @carvana.authentication-flows/shared 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 @carvana.authentication-flows/shared part of a known attack campaign?

Yes — @carvana.authentication-flows/shared is associated with the IN-MAL-2026-007608 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 @carvana.authentication-flows/shared 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 @carvana.authentication-flows/shared (version 19.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @carvana.authentication-flows/shared across your stack and pipelines.

Malicious package

@carvana.authentication-flows/sharednpm

Malicious code in @carvana.authentication-flows/shared (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6521

Immediate action

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

npm uninstall @carvana.authentication-flows/shared

What this malware does

package.json declares a preinstall hook (node index.js) that runs unconditionally on npm install. index.js imports child_process/os/https, collects host identifiers (os.hostname, os.userInfo, platform, arch, homedir, cwd) and shells out to whoami/id, then POSTs the collected JSON to a hardcoded Burp Collaborator subdomain at https://pleq9pugrugzr4zgyymazmnq0h68u4it.oastify.com/detox56. The package name also impersonates the Carvana org by using a . in the scope (@carvana.authentication-flows/shared), making carvana.authentication-flows a fake top-level npm scope rather than a Carvana-owned namespace. There is no legitimate functionality shipped; the package's sole effect on install is reconnaissance exfiltration to an attacker-controlled out-of-band server.

Malicious versions

1 flagged

19.2.1

Indicators of compromise (SHA-256)

78538bf70d1ebd3e4cd784d90b3961ea7966ce9b97e8124110374cad95c0b894

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

Campaign

IN-MAL-2026-007608

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @carvana.authentication-flows/shared-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