Which versions of c11dff444 are malicious?

The following npm versions of c11dff444 are flagged malicious: 1.0.3, 1.0.8, 1.0.10. Treat any of these as compromised.

How do I remediate c11dff444 if I installed it?

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

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

Yes — c11dff444 is associated with the GHSA-cpcr-74hm-pg3c 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 c11dff444 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 c11dff444 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging c11dff444 across your stack and pipelines.

Malicious package

c11dff444npm

Malicious code in c11dff444 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-616

Immediate action

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

npm uninstall c11dff444

What this malware does

The package c11dff444 was found to contain malicious code.

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 'c11dff444' @ 1.0.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged

1.0.31.0.81.0.10

Indicators of compromise (SHA-256)

d9a111c423aac4b02542ff012a7301fa37f42c59fdd1f1fbc0cf647a6cf8e4fb

32eeb31f4d01df3a702777816f89001879d950e05cfad09c16f9ba76c21c2337

800e421e3f7c0652d5a0864ccd5d0eb76bdeb75f89e9550429fd0ddda674367b

4d47b3f981fe050f2eab507069b880d1c47c4107c28eba0d1a16010400a249ad

437d8651f7d884d1905e0d01e2accffb3fcce5408fc4a6b0ef2ca6c37f0bade4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for c11dff444 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging c11dff444 across your stack and pipelines.
If you installed it — respond
Remove c11dff444 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 c11dff444 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 c11dff444 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. c11dff444 on npm has been identified as a malicious package (versions 1.0.3, 1.0.8, 1.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cpcr-74hm-pg3c

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks c11dff444-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