Which versions of jsonschemavalid are malicious?

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

How do I remediate jsonschemavalid if I installed it?

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

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

Yes — jsonschemavalid is associated with the 2026-07-jsonschemavalidation 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 jsonschemavalid 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 jsonschemavalid (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 jsonschemavalid across your stack and pipelines.

Malicious package

jsonschemavalidPyPI

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

MAL-2026-6970

Immediate action

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

pip uninstall jsonschemavalid

What this malware does

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)

66c7a352526170a98abaa8fcccfd433c9e8326e340df4904adce19bd13a05902

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 jsonschemavalid (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 jsonschemavalid across your stack and pipelines.
If you installed it — respond
jsonschemavalid 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 jsonschemavalid 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 jsonschemavalid 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. jsonschemavalid 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-jsonschemavalidation

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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