What does the google-search-result malware do?

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: GENERIC-questionable-pentest Reasons (based on the campaign): - exfiltration-env-variables - exfiltration-generic - The package overrides the install command in setup.py to execute malicious code during installation. - typosquatting The OpenSSF Package Analysis project identified 'google-search-result' @ 2.4.3 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malici

Which versions of google-search-result are malicious?

The following PyPI versions of google-search-result are flagged malicious: 2.4.3. Treat any of these as compromised.

How do I remediate google-search-result if I installed it?

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

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

Yes — google-search-result is associated with the GENERIC-questionable-pentest 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 google-search-result across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for google-search-result (version 2.4.3).

Malicious package

google-search-resultPyPI

Advisory published Feb 12, 2026Updated Feb 13, 2026

google-search-result is a confirmed malicious PyPI package (MAL-2026-874) that steals credentials and exfiltrates sensitive data (malicious version 2.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in google-search-result (PyPI)

MAL-2026-874

Immediate action

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

pip uninstall google-search-result

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

The OpenSSF Package Analysis project identified 'google-search-result' @ 2.4.3 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

2.4.3

Indicators of compromise (SHA-256)

2532d867a44422c3a065c3ba13d63ca9fd446915c2c49aee0877aba997c0a450

7ada4db6050e81933dbf7a82d659e0793c79b0b8f771b3175b5ef4668563238a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for google-search-result (version 2.4.3).
If you installed it — respond
google-search-result 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 google-search-result 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. google-search-result on PyPI has been identified as a malicious package (version 2.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks google-search-result-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