Which versions of gateway-framework are malicious?

The following PyPI versions of gateway-framework are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate gateway-framework if I installed it?

Remove gateway-framework from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed gateway-framework — how do I know if it already compromised me?

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

Yes — gateway-framework is associated with the RLMA-2025-03599, GENERIC-simple-tests, RLUA-2026-00347 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 gateway-framework 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 gateway-framework (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gateway-framework across your stack and pipelines.

Malicious package

gateway-frameworkPyPI

Malicious code in gateway-framework (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6508

Immediate action

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

pip uninstall gateway-framework

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

d2da365e9616185da61b85951de9b3efc6ec6d0c8bbeca0155037179eba52804

2fca15b2080e2437306eba6187b73f2590f24d92c4426b7090cd82a4f164e328

33e0ce8e8a78a4b09b337e8d44727b1c6c268f192890d620881496df3b087f0b

dd7109c83ed581499d3b0dcbc79536a847c2256c8f761eeb9678f492f2013ea1

483c0239d4388b2f7e522c50227483df44967ac7b643bc9560d1343b5d3054bf

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gateway-framework (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gateway-framework across your stack and pipelines.
If you installed it — respond
Remove gateway-framework from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If gateway-framework 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 gateway-framework 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. gateway-framework on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03599GENERIC-simple-testsRLUA-2026-00347

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks gateway-framework-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring