Which versions of jsonschemavalidation are malicious?

The following PyPI versions of jsonschemavalidation are flagged malicious: 4.26.0. Treat any of these as compromised.

How do I remediate jsonschemavalidation if I installed it?

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

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

Yes — jsonschemavalidation is associated with the 2026-07-jsonschemavalidation, IN-MAL-2026-008960 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 jsonschemavalidation 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 jsonschemavalidation (version 4.26.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonschemavalidation across your stack and pipelines.

Malicious package

jsonschemavalidationPyPI

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

MAL-2026-6945

Immediate action

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

pip uninstall jsonschemavalidation

What this malware does

The PyPI project jsonschemavalidation builds a wheel whose installed top-level package is literally jsonschema ([tool.hatch.build.targets.wheel] packages = ["src/jsonschema"]). Project metadata (author name, homepage pointing at github.com/python-jsonschema/jsonschema, README, description) mirrors the legitimate upstream jsonschema project. Installing this distribution places files into the real jsonschema import namespace on the installer, so import jsonschema in downstream code would resolve to the code shipped by this distribution rather than the genuine one. The current 4.26.0 contents appear to be an unmodified copy of upstream and no exfiltration, install-time fetch-and-execute, credential harvesting, silent-relay, backdoor, or other installer-harm payload is present in this version. The concern is the namespace-collision channel itself: a name-confusion distribution that populates a widely-used import name is a plausible squat/hijack setup, but name-similarity and namespace collision alone are subjective signals without a payload, so human review is appropriate rather than an automatic block.

A clone of a legitimate package with an embeded reverse shell. In the published version, the reverse shell was connecting to a private IP address suggesting the package was not yet fully weaponized.

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

Campaign: 2026-07-jsonschemavalidation

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
clones-real-package
obfuscation

Malicious versions

1 flagged

4.26.0

Indicators of compromise (SHA-256)

b7a6e1ff837eac0382559815111106e3e85b3825b72f38355551d5874cc24b0e

eae82aa94c358f1f00f8a12e8b583cee82efdcf09d2f80263e6851ac0fec98f3

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

Campaign

2026-07-jsonschemavalidationIN-MAL-2026-008960

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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