Which versions of websynapse are malicious?

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

How do I remediate websynapse if I installed it?

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

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

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

Malicious package

websynapsePyPI

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

MAL-2025-1007

Immediate action

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

pip uninstall websynapse

What this malware does

The package contains highly obfuscated content, that install another, downloaded from a remote location obfuscated script in the installation path of the 'requests' package, and marks it as a hidden system file. In addition, another file contains a code that imitates doing some meaningful activity.

Later attempts hide the malicious code in a separated package, downloaded from Test PyPI.

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

Campaign: 2024-12-httpfluent

Reasons (based on the campaign):

obfuscation
modify-system-without-consent
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

ee2936003f3c2b566185ee1da7d9c1e796e74e535697e316c78f9ff5dbc19419

688101a5863f3e70cdc1a3dd9bb5c185aac5830d464c96708692751754ff1f52

7323a05444284204de7701ff8b7a738bc155cb22356cf93fc1399dedad5afa46

0b12e14b6501d74057ec4174ec2a32f6d9fd8f192385ed93327aebd6390a099c

39a337d3317c832f39c6d26a020f5f9ac3152e237645ee2215dbfb83eaea30cc

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 websynapse (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging websynapse across your stack and pipelines.
If you installed it — respond
websynapse 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 websynapse 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 websynapse 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. websynapse 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-2025-005482024-12-httpfluentRLUA-2026-00926

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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