Which versions of django-aerospike-sessions are malicious?

The following PyPI versions of django-aerospike-sessions are flagged malicious: 5.0.0. Treat any of these as compromised.

How do I remediate django-aerospike-sessions if I installed it?

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

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

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

Malicious package

django-aerospike-sessionsPyPI

Malicious code in django-aerospike-sessions (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47758

Immediate action

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

pip uninstall django-aerospike-sessions

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

5.0.0

Indicators of compromise (SHA-256)

dd9da9e3bf4087f7d7655332607cbcbad0bf8ac254780cdbd8c21b2157a8f0a8

2ef43f7435924f20235385d6ffb4ad88a2a131ae650dbb4dcc0327124e463515

feba434f8a55ca606e9301308486d6d3d6f518430157438198d692432c18da23

147bfdfda49ee96b1717becab3b105781484193b532d254dd2a050d2b0848ef6

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

Campaign

RLMA-2025-04759GENERIC-standard-pypi-install-pentestRLUA-2026-00277

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks django-aerospike-sessions-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