Which versions of get-incorrect-name-bob are malicious?

The following PyPI versions of get-incorrect-name-bob are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate get-incorrect-name-bob if I installed it?

get-incorrect-name-bob 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 get-incorrect-name-bob — how do I know if it already compromised me?

If get-incorrect-name-bob 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 get-incorrect-name-bob part of a known attack campaign?

Yes — get-incorrect-name-bob is associated with the GENERIC-standard-pypi-install-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 get-incorrect-name-bob 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 get-incorrect-name-bob (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 get-incorrect-name-bob across your stack and pipelines.

Malicious package

get-incorrect-name-bobPyPI

Malicious code in get-incorrect-name-bob (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-862

Immediate action

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

pip uninstall get-incorrect-name-bob

What this malware does

While disguised as a dummy MCP server, the only real functionality is exfiltrating hostname on importing.

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-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

5cb10edcf75f6463de2adaa0a621cf5fb215b5431a87d36a3b94e1910fb774ab

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

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks get-incorrect-name-bob-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