Which versions of httpsyncer are malicious?

The following PyPI versions of httpsyncer are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate httpsyncer if I installed it?

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

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

Yes — httpsyncer is associated with the RLMA-2025-04178, 2025-08-dsidelib, RLUA-2026-00402 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 httpsyncer 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 httpsyncer (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging httpsyncer across your stack and pipelines.

Malicious package

httpsyncerPyPI

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

MAL-2025-41686

Immediate action

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

pip uninstall httpsyncer

What this malware does

Package is runs an Infostealer targeting telegram and Discord credentials. Depending on version, the infostealer is either downloaded from an URL or embedded in the package

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

Campaign: 2025-08-dsidelib

Reasons (based on the campaign):

infostealer
Downloads and executes a remote malicious script.
exfiltration-browser-data
target:telegram

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

baeae37e1174204bc135a09c5dfed562bcca48d347375141ba25609b4fb9ccd1

28596981d86a001cf204b04afc8e53ffc504e755765f8b4a87cd56fa5213e42a

3e9323dbc11b949e9970ead2dcc1c5a7f05348a977591f8c86027ee220c86b62

b700f5e445c5f321d670ea3920eae22fc6905ee1daa07e63d98580ae2c38c2cd

2552d0f681d317319dfea5f2abb35526bd858cd33b4de4706dea7ebdd378633a

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

Campaign

RLMA-2025-041782025-08-dsidelibRLUA-2026-00402

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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