Which versions of keras-preprocess are malicious?

The following PyPI versions of keras-preprocess are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate keras-preprocess if I installed it?

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

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

Yes — keras-preprocess is associated with the 2024-11-byted-dast 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 keras-preprocess 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 keras-preprocess (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging keras-preprocess across your stack and pipelines.

Malicious package

keras-preprocessPyPI

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

MAL-2024-10649

Immediate action

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

pip uninstall keras-preprocess

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'keras-preprocess' @ 94.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

94.6

Indicators of compromise (SHA-256)

615e1927f6d9cec9f0436d81510a012a2875ef413ac8bc5e11c3a6c341d3190b

25e2e2bcc6c53208018ee2417f0b96f0863b6579e5248be57baf7fbd35b77722

c153be1503b6ad6b4b2a00de177c76a28d50f4612220edb1dcebf6ac85812ba2

e316317937ce69e58adea7fc1f7ce9e2c8238e56bf8b14517e17987f106e83a8

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks keras-preprocess-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