Which versions of weorewfoi2393 are malicious?

The following PyPI versions of weorewfoi2393 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate weorewfoi2393 if I installed it?

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

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

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

Malicious package

weorewfoi2393PyPI

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

MAL-2025-192993

Immediate action

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

pip uninstall weorewfoi2393

What this malware does

Package tests possible malicious actions during installation by starting notepad. There is no other functionality, it's clearly a test of possible malicious actions.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

00296490bb9bcec28af256a76790f8c5f96dd45d4184ac6617bbdffad3e674a3

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

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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