Which versions of alksdjpureranser are malicious?

The following PyPI versions of alksdjpureranser are flagged malicious: 3.0.0. Treat any of these as compromised.

How do I remediate alksdjpureranser if I installed it?

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

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

Yes — alksdjpureranser is associated with the RLMA-2025-03514, GENERIC-standard-pypi-install-pentest, RLUA-2026-00059 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 alksdjpureranser 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 alksdjpureranser (version 3.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging alksdjpureranser across your stack and pipelines.

Malicious package

alksdjpureranserPyPI

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

MAL-2025-6430

Immediate action

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

pip uninstall alksdjpureranser

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

3.0.0

Indicators of compromise (SHA-256)

754c3f22f3107eb21dfdad0b56ff3108b333018aa1396f60788e7da7d14e2299

1ffc3360c7320969208281ce02de942bbdaf5ad7cf220e82347c47b22fba42ac

7d4a7e9cfee7bc0812dbc2462faaa4bd791f84c5e432b0416429056fd20ec2ca

dfa28e41edf088fa46167332cc76d23744bed638ed630898269418d1408403a4

4619b69db27684fc13c0853df97bd5bcf89d19c0929a343c027c7ec8129d0e86

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

Campaign

RLMA-2025-03514GENERIC-standard-pypi-install-pentestRLUA-2026-00059

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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