Which versions of google-appengine-ext are malicious?

The following PyPI versions of google-appengine-ext are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate google-appengine-ext if I installed it?

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

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

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

Malicious package

google-appengine-extPyPI

Malicious code in google-appengine-ext (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6512

Immediate action

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

pip uninstall google-appengine-ext

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

Indicators of compromise (SHA-256)

827b9906f790b75c203043629ce8ff719da6b3ee8691c162d44b6b4b26c8f4d4

fcdf613be66e5f3f0cd550dda9240042bc79aeed78abe3db101b1b38d9ef725f

142a8fbc789954291f2b01aab5ac1d139eaaf4f9f490fd6dcf30da438f7d8e51

98b9157bdd105e9be9c5beb53c77fa733bc24fe59ade3020427d3e58e47dde48

3f93c13c6e2e936174d442890860d141f4eaf81a96d2fa4ef7e235b15fbe84b0

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

Campaign

RLMA-2025-03603GENERIC-standard-pypi-install-pentestRLUA-2026-00359

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks google-appengine-ext-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