Which versions of goftvagoo are malicious?

The following PyPI versions of goftvagoo are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate goftvagoo if I installed it?

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

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

Yes — goftvagoo is associated with the RLMA-2025-00469, GENERIC-standard-pypi-install-pentest, RLUA-2026-00357 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 goftvagoo 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 goftvagoo (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging goftvagoo across your stack and pipelines.

Malicious package

goftvagooPyPI

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

MAL-2025-930

Immediate action

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

pip uninstall goftvagoo

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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.1

Indicators of compromise (SHA-256)

e7401863288c1efcd49e0503d21e26c5a6d4feff4ae417319bc41893688b6d6f

f566705391f5b9b15ed8a9af11b92948741dd44b43c8b2579ce8b5f1d3cc456a

01320e94594824575e43d50e625ddc317b88604ca070ab58b5b5cb265826879f

0527396d6b454d027160858fbb1b6af3218e02d536651614b554f649d724793c

1171f0743af7ad61c897989dd46f4236c7a73925a2b0d0e1407e9c82bbe45429

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

Campaign

RLMA-2025-00469GENERIC-standard-pypi-install-pentestRLUA-2026-00357

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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