Which versions of soundsource are malicious?

The following PyPI versions of soundsource are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate soundsource if I installed it?

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

If soundsource was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is soundsource part of a known attack campaign?

Yes — soundsource is associated with the IN-MAL-2026-003268 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 soundsource across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for soundsource (version 0.1.0).

Malicious package

soundsourcePyPI

Advisory published May 19, 2026Updated May 26, 2026

soundsource is a confirmed malicious PyPI package (MAL-2026-4769) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in soundsource (PyPI)

MAL-2026-4769

Immediate action

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

pip uninstall soundsource

What this malware does

The package's source distribution contains Token.txt at the tarball root holding a live PyPI API token (prefix pypi-AgEIcHlwaS5vcmc...). Anyone who downloads or installs the sdist obtains a credential granting publish rights on PyPI under the author's account, enabling republication of trojaned versions of this package (and any other package within the token's scope) to all downstream installers. Additional quality concerns include a malformed Homepage URL in pyproject.toml (https://https://github.com/...) and a placeholder DEFAULT_BASE_URL pointing at api.soundsource.example.com, indicating an unreviewed publish.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

e3285c5fec24c01c9c463e85c199934f5a08da7e94277583430a6e3feb274add

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for soundsource (version 0.1.0).
If you installed it — respond
soundsource 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 soundsource was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. soundsource on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003268

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database