Which versions of jsonschemex are malicious?

The following PyPI versions of jsonschemex are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5. Treat any of these as compromised.

How do I remediate jsonschemex if I installed it?

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

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

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

Malicious package

jsonschemexPyPI

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

MAL-2025-191769

Immediate action

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

pip uninstall jsonschemex

What this malware does

Malicious clone of a legitimate package with hidden code that downloads the next stage scripts. Analysed payloads had just exfiltrated basic infos

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-11-jsonschemex

Reasons (based on the campaign):

exfiltration-generic
obfuscation
clones-real-package
Downloads and executes a remote malicious script.

Malicious versions

6 flagged

0.1.00.1.10.1.20.1.30.1.40.1.5

Indicators of compromise (SHA-256)

cb95029bef5c706aa59051a453164f0e30372164286db344ccc952db4b332004

21f678f82847db32c68ab5a95a827f755d13b5d4cd371667eb584f25ed28ed01

68be8e9596105ad16c289bc56b643806e1bbea5e5ab37f7c72a1bc845170c2c7

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

Campaign

2025-11-jsonschemex

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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