Which versions of nezur are malicious?

The following PyPI versions of nezur are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate nezur if I installed it?

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

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

Yes — nezur is associated with the RLMA-2024-11103, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00556 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 nezur 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 nezur (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nezur across your stack and pipelines.

Malicious package

nezurPyPI

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

MAL-2024-11647

Immediate action

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

pip uninstall nezur

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

cf992ff1f7128e1734a22811fae6e517fdfb03f9e3aa0f87ae65b0caa0771070

b13151355ad15c1d42c644bb51017f23f21f8cf78f77df5c31cc40b24b70db7a

b50feb48c96e1118a7a347159715ad52cef02efdc463783eb9edcc5f33b6bbad

80e8bd5eb464fb041c5ddf612ad6513cedb7657df545ca16f1621066fcfccf1d

8dcbf1b0efb798083433fb43fa0d4659ef11bb133a14aac909c777c7bf650f9c

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

Campaign

RLMA-2024-111032024-08-embeds-RealtekHDAudioManagerRLUA-2026-00556

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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