Which versions of swisscom-ai-research-keyphrase are malicious?

The following PyPI versions of swisscom-ai-research-keyphrase are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate swisscom-ai-research-keyphrase if I installed it?

swisscom-ai-research-keyphrase 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 swisscom-ai-research-keyphrase — how do I know if it already compromised me?

If swisscom-ai-research-keyphrase 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 swisscom-ai-research-keyphrase part of a known attack campaign?

Yes — swisscom-ai-research-keyphrase is associated with the GENERIC-beacon-dependency-confusion 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 swisscom-ai-research-keyphrase 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 swisscom-ai-research-keyphrase (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swisscom-ai-research-keyphrase across your stack and pipelines.

Malicious package

swisscom-ai-research-keyphrasePyPI

Malicious code in swisscom-ai-research-keyphrase (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3046

Immediate action

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

pip uninstall swisscom-ai-research-keyphrase

What this malware does

Package exploits dependency confusion. A beacon request is used to report usage back, but no additional information are exfiltrated.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-beacon-dependency-confusion

Reasons (based on the campaign):

typosquatting
dependency-confusion

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

e11009ce6f39424ab9bbe1470888a9f5be4f1252dab4c82a03d684d372eb7cc9

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

Campaign

GENERIC-beacon-dependency-confusion

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks swisscom-ai-research-keyphrase-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