Which versions of websend are malicious?

The following PyPI versions of websend are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate websend if I installed it?

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

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

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

Malicious package

websendPyPI

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

MAL-2024-11749

Immediate action

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

pip uninstall websend

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.0.1

Indicators of compromise (SHA-256)

55776610602aa2288c566d5b99fe67dfcf86bc888a1105fb0d3e490d03918589

374205ece6413a1e7db317e306baba28187a4d551eddbb35d5030e006f8e3cd7

34f01e1b145ba4aed5b39af44bab870ab9406bc9e98d8f1f92354901189e7e2e

19001a5b203115a8d45aa329ff76d6bac8d81a5b7939935f5ca5300513adfafc

33f026a0d297abea3995294cabca36006f3963b1185507fa780cfbed62c98d01

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

Campaign

RLMA-2024-112112024-08-embeds-RealtekHDAudioManagerRLUA-2026-00924

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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