Which versions of pam98wyfupa98w are malicious?

The following PyPI versions of pam98wyfupa98w are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pam98wyfupa98w if I installed it?

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

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

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

Malicious package

pam98wyfupa98wPyPI

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

MAL-2025-191810

Immediate action

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

pip uninstall pam98wyfupa98w

What this malware does

Importing the module starts a reverse shell

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

Campaign: 2025-11-d1n0

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c8b62ee93d374187e728b0d24a516ffcd4f3a209bf5214a3c3c1587f225a3e92

be7177fd2d56b518724377233ca5eda13a07f6252e400cfb4c1115db456b5fd8

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

Campaign

2025-11-d1n0

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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