Which versions of dependency908 are malicious?

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

How do I remediate dependency908 if I installed it?

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

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

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

Malicious package

dependency908PyPI

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

MAL-2025-915

Immediate action

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

pip uninstall dependency908

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)

917b573e14782d715c3a9be254f0febf1aeef59dfc81a6225eb0a4227f73f34c

4191178db4ed02aa872bc186d40c998d50a93fff7c2edc2a91e57b0a97dec035

25814cf8cbc379ad2210acacd5990c5457e8d4c7b2e6046a02a628cdfa555c9d

b1d6624169e8b51b055b4dfb112cb443989f6ff808f18314f184d476d9dfeffd

952e1e80354a2694bbcdf94d8b2cf0ca5702aa2c6c89431d0222f430cbaf61b0

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 dependency908 (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 dependency908 across your stack and pipelines.
If you installed it — respond
dependency908 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 dependency908 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 dependency908 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. dependency908 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-00454GENERIC-standard-pypi-install-pentestRLUA-2026-00258

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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