Which versions of firestore-lite are malicious?

The following npm versions of firestore-lite are flagged malicious: 45.0.0. Treat any of these as compromised.

How do I remediate firestore-lite if I installed it?

firestore-lite is a typosquat — you almost certainly intended a legitimately-named package. Remove firestore-lite, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed firestore-lite — how do I know if it already compromised me?

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

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

Malicious package

firestore-litenpm

firestore-lite is a confirmed malicious npm package (MAL-2026-15534) that typosquats a legitimate package to trick installs (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in firestore-lite (npm)

MAL-2026-15534

Immediate action

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

npm uninstall firestore-lite

What this malware does

package.json declares a single dependency whose value is a bare HTTP URL (https://repo.securityctrl.com/firestore-lite) rather than a registry version range. On npm install, npm fetches and installs whatever tarball that URL returns, running any lifecycle scripts contained in it, with no version pin and no integrity check. The dependency key is the package's own name, a dependency-confusion shape, and the shipped index.js is an inert stub — the manifest line is the entire published payload. The package name mimics the legitimate Firebase 'firestore-lite' module, and the version 45.0.0 is implausibly high for that name, consistent with an attempt to win version resolution against an internal package.

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

3242d5a15b769961bcc2e6d24747a7da27e2afd293ea83e6b042eceeb4b97de2

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for firestore-lite (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging firestore-lite across your stack and pipelines.
If you installed it — respond
firestore-lite is a typosquat — you almost certainly intended a legitimately-named package. Remove firestore-lite, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If firestore-lite 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 firestore-lite 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. firestore-lite on npm has been identified as a malicious package (version 45.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019096

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks firestore-lite-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