Which versions of pulsecord are malicious?

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

How do I remediate pulsecord if I installed it?

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

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

Yes — pulsecord is associated with the 2025-11-discord-selfsbotsx 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 pulsecord 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 pulsecord (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 pulsecord across your stack and pipelines.

Malicious package

pulsecordPyPI

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

MAL-2025-191830

Immediate action

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

pip uninstall pulsecord

What this malware does

This package is prepared for silent execution of a malicious executable, with disabling AV protection. While there is no link to the malicious binary inside, the package shares clear indicators of being part of the 2025-11-discord-selfsbotsx campaign.

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

Campaign: 2025-11-discord-selfsbotsx

Reasons (based on the campaign):

Downloads and executes a remote executable.
infostealer
malware
peristence-autorun

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5a6f1f7e308990c5a418b218c6a0cd099913b244d8a5d6fb3aca59dbfc1cd1c1

025d4e33a2037fb9ad36cb4b08b122e4439bb4932b73ac6c6f403609e7e1c09e

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 pulsecord (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 pulsecord across your stack and pipelines.
If you installed it — respond
pulsecord 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 pulsecord 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 pulsecord 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. pulsecord 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

2025-11-discord-selfsbotsx

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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