Which versions of @factoryz/apollo are malicious?

The following npm versions of @factoryz/apollo are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @factoryz/apollo if I installed it?

Remove @factoryz/apollo 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 @factoryz/apollo — how do I know if it already compromised me?

If @factoryz/apollo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @factoryz/apollo part of a known attack campaign?

Yes — @factoryz/apollo is associated with the IN-MAL-2026-021693 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 @factoryz/apollo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @factoryz/apollo (version 99.9.1).

Malicious package

@factoryz/apollonpm

Advisory published Oct 25, 2026Updated Oct 25, 2026

@factoryz/apollo is a confirmed malicious npm package (MAL-2026-18278) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @factoryz/apollo (npm)

MAL-2026-18278

Immediate action

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

npm uninstall @factoryz/apollo

What this malware does

The package ships only an empty stub (module.exports = {}) and a manifest whose sole dependency ltidisafe is resolved from a hardcoded off-registry HTTPS URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.7.tgz) rather than a registry version range. npm install @factoryz/apollo fetches whatever bytes that URL returns and installs them, executing any lifecycle scripts (preinstall/install/postinstall) contained in the fetched tarball. There is no version pin, no integrity (sshasum) check, and no publisher binding — the host controller can swap the tarball contents at any time. The version number 99.9.1 is implausibly high for a package whose shipped code is a one-line stub, consistent with a dependency-confusion / resolution-winning shape. The lure package itself contains no other logic; the manifest IS the payload.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

5adaa62818c76a10cbf0b536a6854633e24a73028c803fc597c5b5ec1d78b8ad

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @factoryz/apollo (version 99.9.1).
If you installed it — respond
Remove @factoryz/apollo 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 @factoryz/apollo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @factoryz/apollo on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021693

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @factoryz/apollo-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