Which versions of wasi8787878 are malicious?

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

How do I remediate wasi8787878 if I installed it?

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

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

Yes — wasi8787878 is associated with the RLMA-2025-00545, GENERIC-standard-pypi-install-pentest, RLUA-2026-00911 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 wasi8787878 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 wasi8787878 (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 wasi8787878 across your stack and pipelines.

Malicious package

wasi8787878PyPI

wasi8787878 is a confirmed malicious PyPI package (MAL-2025-1004) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wasi8787878 (PyPI)

MAL-2025-1004

Immediate action

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

pip uninstall wasi8787878

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
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)

c58ce35e19ef5d66bc0fb8a8052ae0fd4eed527a7304443f6d67eb440fa80f4d

48dcc2d758e3f7f7ddf5d76cb51ee4a4e734a54a4f64772b2a5968f461fcfa78

e7e8dad2dca9000e3bd94355a78838c2c9448aac766722cfd54aba1fc5c2cd43

449654d42e6a1f72d2df6a76d2f1a00de0466fd58e803106df52461c3a42c70a

57eb0c8bd925dd581bd3a8fadb65e238c6c3272e98d9471833719d8eee5455ab

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 wasi8787878 (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 wasi8787878 across your stack and pipelines.
If you installed it — respond
wasi8787878 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 wasi8787878 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 wasi8787878 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. wasi8787878 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

RLMA-2025-00545GENERIC-standard-pypi-install-pentestRLUA-2026-00911

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database