Which versions of progerss-cli are malicious?

The following npm versions of progerss-cli are flagged malicious: 3.12.0. Treat any of these as compromised.

How do I remediate progerss-cli if I installed it?

progerss-cli 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 progerss-cli — how do I know if it already compromised me?

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

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

Malicious package

progerss-clinpm

Malicious code in progerss-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5343

Immediate action

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

npm uninstall progerss-cli

What this malware does

progerss-cli is a typosquat of the popular cli-progress package that ships an obfuscated payload executed automatically on install.

The package borrows trust from its victim: repository.url is set to https://github.com/npkgz/cli-progress — the legitimate cli-progress project's own repository — and the author field is set to andidittrich (the real maintainer).

package.json defines scripts.postinstall: node build-helper.js, and declares form-data as its only runtime dependency (used for exfiltration).

build-helper.js (load gate): polls up to 31 times at 1.5 s intervals for form-data to resolve (require.resolve('form-data')), then require('./index.js'). This delays payload execution until the exfiltration dependency is fully installed, evading naive install-time analysis that runs before dependencies settle.

index.js: a ~273 KB obfuscated payload that performs data collection and form-data-based HTTP exfiltration.

Package name 'progerss-cli' resembles the common spelling 'progress-cli' via a two-character transposition, which is a typical typosquat shape. No exfiltration, dropper, credential access, or other installer-harm behavior was observed in the scanned files, and no lifecycle scripts were identified. Without a confirmed payload, name similarity alone is not sufficient to block, but the naming pattern warrants human review to assess intent and impact on installers who mistype a target package name.

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

1 flagged

3.12.0

Indicators of compromise (SHA-256)

7fde91dd01fb8e69b5fcf0130d7fc0e5d08b1820413452ed0d72ce42d06e6dab

ea4c1c3b9761cfe244327e4937c18585ef6fc901df383b24c3f0e148c195e8f7

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

Campaign

GHSA-pr99-g8pf-f3rrIN-MAL-2026-008619

References

Credits

Amazon Inspector · finder
Hugo Guillaume (Konvu) · finder

Detect & block this

O3 blocks progerss-cli-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