Which versions of depcruise-fmt are malicious?

The following npm versions of depcruise-fmt are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate depcruise-fmt if I installed it?

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

I already installed depcruise-fmt — how do I know if it already compromised me?

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

Yes — depcruise-fmt is associated with the IN-MAL-2026-017977, GHSA-gh2x-96f9-2cgf 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 depcruise-fmt 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 depcruise-fmt (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging depcruise-fmt across your stack and pipelines.

Malicious package

depcruise-fmtnpm

depcruise-fmt is a confirmed malicious npm package (MAL-2026-14054) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in depcruise-fmt (npm)

MAL-2026-14054

Immediate action

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

npm uninstall depcruise-fmt

What this malware does

depcruise-fmt ships an empty module (index.js exports {}) and declares its only dependency, ltidisafe, as an arbitrary HTTPS tarball hosted at https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.3.tgz rather than a registry package. On npm install, npm fetches and installs that off-registry tarball into the dependency tree and executes any lifecycle scripts it contains. The wrapper package has no other functionality — its sole effect is to inject the externally hosted payload. The tarball is served from an author-controlled Google Cloud Storage bucket, is not subject to registry publish scanning, is not integrity-pinned, and its contents can be replaced at any time without a corresponding npm publish. The package name also resembles the popular dependency-cruiser tooling, positioning this as a lookalike lure whose only installation effect is to resolve to the GCS-hosted tarball.

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.

The OpenSSF Package Analysis project identified 'depcruise-fmt' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

ea193e6cea73a06c8f92a684d56040564d6a0fef93da1d45010978107ea0fd0c

08675f5d3de6c71d05588ae719204e2919ffac836aaada2f24b2b61bed2291ba

fcb3bc16724ee86eb43e9d012953d05ef1181b3fbffb92480776a5c8b39c06e4

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 depcruise-fmt (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging depcruise-fmt across your stack and pipelines.
If you installed it — respond
depcruise-fmt is a typosquat — you almost certainly intended a legitimately-named package. Remove depcruise-fmt, 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 depcruise-fmt 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 depcruise-fmt 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. depcruise-fmt 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-017977GHSA-gh2x-96f9-2cgf

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks depcruise-fmt-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