Which versions of ledgerflow-deploy-utils are malicious?

The following npm versions of ledgerflow-deploy-utils are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate ledgerflow-deploy-utils if I installed it?

ledgerflow-deploy-utils 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 ledgerflow-deploy-utils — how do I know if it already compromised me?

If ledgerflow-deploy-utils 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 ledgerflow-deploy-utils part of a known attack campaign?

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

Malicious package

ledgerflow-deploy-utilsnpm

Malicious code in ledgerflow-deploy-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6591

Immediate action

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

npm uninstall ledgerflow-deploy-utils

What this malware does

On npm install, the package's postinstall script queries the AWS instance metadata service (IMDSv1) at 169.254.169.254 for the attached IAM role and POSTs the result, along with an IMDS-reachability probe, over plain HTTP to a hardcoded bare IP (54.226.194.239:80/chain3). The published library surface (index.js) only exports two no-op console.log stubs named validate/deploy, with no real functionality — the entire effective behavior is the install-time reconnaissance against AWS-hosted installers and CI runners. The combination of a placeholder API, a generic deployment-utility name suggesting an internal/private package, and install-time recon to a hardcoded bare-IP C2 matches the dependency-confusion / internal-name-squat pattern targeting corporate build systems, where exposed IAM role names enable follow-on credential abuse against the installer's cloud environment.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

5f0097d19be676ac30ff79dffcff38f128873c80115a8a150c3eceff0422aa93

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

Campaign

IN-MAL-2026-007771

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ledgerflow-deploy-utils-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