Which versions of sendtowev are malicious?

The following PyPI versions of sendtowev are flagged malicious: 0.1, 0.2, 0.3, 0.4. Treat any of these as compromised.

How do I remediate sendtowev if I installed it?

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

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

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

Malicious package

sendtowevPyPI

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

MAL-2024-11704

Immediate action

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

pip uninstall sendtowev

What this malware does

Package contains CStealer, a known infostealer, starting on importing the module.

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

Campaign: 2024-09-cstealer

Reasons (based on the campaign):

infostealer
infostealer:cstealer

Malicious versions

4 flagged

0.10.20.30.4

Indicators of compromise (SHA-256)

3a6490a8b8c2198937fd37dfdb7bc44b5164606113d80fb6b17de804ab94d3b0

a91b642c075e2e96d100a8c7a1c046c374dac6ba7683e3ec6a64f9a7795ea4fd

bee6e22271136b92077edad317e9a1e3eaa120bba73814159142d522cba12ced

5a01de774c00219d773b617bfcef15ae8dda2ebe4f8fbb66cf10d78125092b76

c323619505e0e8f3f1a5fce207f100a3b00670d5949fda8ef55cf4aabc9ef192

03bc26064487b4fb377064375084cc46ba112494dc88f9e52039cb29d6ef61cc

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

Campaign

RLMA-2024-111622024-09-cstealerRLUA-2026-00751

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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