Which versions of coffin2022 are malicious?

The following PyPI versions of coffin2022 are flagged malicious: 7.0. Treat any of these as compromised.

How do I remediate coffin2022 if I installed it?

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

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

Yes — coffin2022 is associated with the 2024-08-old-coffins-tunnel 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 coffin2022 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 coffin2022 (version 7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coffin2022 across your stack and pipelines.

Malicious package

coffin2022PyPI

Malicious code in coffin2022 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12245

Immediate action

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

pip uninstall coffin2022

What this malware does

So far, it looks like a legit tunneling software, but in tcp.py there is an attempt to send a strange email using gmail. Update: Identified as malicious by socket.dev team

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-08-old-coffins-tunnel

Reasons (based on the campaign):

crypto-related

Malicious versions

1 flagged

7.0

Indicators of compromise (SHA-256)

c619ce983137ded3d34941bd6ef4893b1546d80c141cb9da36cbf122e4aef971

2f875ec44c758a726a21474b433c8f43af3d2ee96a3bdcca60f75288316b95ae

7ac2db08cc88b0b26ee8c0ddeef399ccc5a870de9173e251a10f164d78934a67

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

Campaign

2024-08-old-coffins-tunnel

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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