Which versions of luna-paysure are malicious?

The following PyPI versions of luna-paysure are flagged malicious: 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.7.5. Treat any of these as compromised.

How do I remediate luna-paysure if I installed it?

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

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

Yes — luna-paysure is associated with the RLMA-2024-11081, 2024-10-luna, RLUA-2026-00483 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 luna-paysure 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 luna-paysure (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging luna-paysure across your stack and pipelines.

Malicious package

luna-paysurePyPI

Malicious code in luna-paysure (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11627

Immediate action

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

pip uninstall luna-paysure

What this malware does

Importing the module causes exfiltrating of IP and hostname.

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: 2024-10-luna

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.

Malicious versions

5 flagged

0.7.10.7.20.7.30.7.40.7.5

Indicators of compromise (SHA-256)

b2a58ca69707b93da5802484ae30cfca081869a0ffd5fe44c63239d4bf7979d9

256e14fe68cfcbdf0319cc71a4f3085d94575497bbad7164062fa9c447091ea1

d22eccc425ab8fc5afe244efb33dd6d500ea6bcdf0942a02dedb3daa9f17da51

e830e6a7c4b9a388ff1cd5c405274755370a46fde5139463a640e6fba87ce53b

72613f2302d16b7c99658c6b16141b0677d75f11db56b4b81f61290daffb68d6

153eff3fba56fe25b7a38871f47b20d458ab80f6d5dc25fdc69947678557d50b

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

Campaign

RLMA-2024-110812024-10-lunaRLUA-2026-00483

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks luna-paysure-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