What does the iwantsafecheckit malware do?

During installation the package downloads and installs two executables identified as backdoors trojans. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-03-thisismytest123 Reasons (based on the campaign): - Downloads and executes a remote executable. - backdoor - malware The OpenSSF Package Analysis project identified 'iwantsafecheckit' @ 2.0.0 (pypi) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of iwantsafecheckit are malicious?

The following PyPI versions of iwantsafecheckit are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate iwantsafecheckit if I installed it?

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

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

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

Malicious package

iwantsafecheckitPyPI

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

MAL-2026-2290

Immediate action

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

pip uninstall iwantsafecheckit

What this malware does

During installation the package downloads and installs two executables identified as backdoors trojans.

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

Campaign: 2026-03-thisismytest123

Reasons (based on the campaign):

Downloads and executes a remote executable.
backdoor
malware

The OpenSSF Package Analysis project identified 'iwantsafecheckit' @ 2.0.0 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

c982c88e841ae349f894f45b27e07f7154a252963ec05ff8e9536f46102e6ecf

388915d99ad3e370a59631112b6a0b784801e257e13f0f9855a2a340c4f068f0

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

Campaign

2026-03-thisismytest123

References

Credits

Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder

Detect & block this

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