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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for soundsource (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soundsource across your stack and pipelines.

Malicious package

soundsourcePyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for soundsource (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soundsource across your stack and pipelines.
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 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 soundsource 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. 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