lychee-norm-cachenpm
lychee-norm-cache is a confirmed malicious npm package (MAL-2026-11029) that steals credentials and exfiltrates sensitive data (malicious version 22.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lychee-norm-cache (npm)
What this malware does
lychee-norm-cache is a dependency-confusion proof-of-concept that provides no functional utility. Its bin script POSTs a small JSON payload containing the package name, a timestamp, and the basename of INIT_CWD (the directory in which npm/npx was invoked) to a hardcoded callback URL at https://deepbounty.dd06-dev.fr/cb/<id>. The package has no install lifecycle scripts and the declared main entry is absent, so the beacon fires only when the bin is explicitly executed (typically via npx, or when this name resolves in place of an intended internal package). The data sent is minimal and non-credential (project directory name only); there is no exfiltration of environment variables, files, or secrets, no remote code execution, and no persistence. However, the package occupies a namespace that may collide with internal package names and silently emits installer-side context to a third-party host without consent.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lychee-norm-cache (version 22.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lychee-norm-cache across your stack and pipelines.
If you installed it — respond
lychee-norm-cache 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 lychee-norm-cache 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 lychee-norm-cache 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks lychee-norm-cache-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.