What does the testjson3 malware do?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-07-ronnyfredd-exfiltr-clipboard Reasons (based on the campaign): - peristence-autorun - clipboard-stealing - The OpenSSF Package Analysis project identified 'testjson3' @ 0.1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of testjson3 are malicious?

The following PyPI versions of testjson3 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate testjson3 if I installed it?

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

If testjson3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is testjson3 part of a known attack campaign?

Yes — testjson3 is associated with the 2024-07-ronnyfredd-exfiltr-clipboard 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 testjson3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testjson3 (version 0.1).

Malicious package

testjson3PyPI

Advisory published Jul 21, 2024Updated Dec 12, 2025

testjson3 is a confirmed malicious PyPI package (MAL-2024-7838) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testjson3 (PyPI)

MAL-2024-7838

Immediate action

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

pip uninstall testjson3

What this malware does

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

Campaign: 2024-07-ronnyfredd-exfiltr-clipboard

Reasons (based on the campaign):

peristence-autorun
clipboard-stealing

The OpenSSF Package Analysis project identified 'testjson3' @ 0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

44b3b78c09f0412b1a13b0871d62ad7afb6b7af0090963945ed503b380ad2e25

f90907b0a30d7bffa6bef2290049071f1502c60eff59173fb49b95a5121887d9

783bce620b6d82880784734f95e5e48217bdc056277d57781a45fb14b66bcb97

23725a4f8bef9ce53c1aa6ed3e8c57ba5e99ff7a9005b310f1cb031dbd2a40d5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for testjson3 (version 0.1).
If you installed it — respond
testjson3 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 testjson3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. testjson3 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-07-ronnyfredd-exfiltr-clipboard

References

bad-packages.kam193.eu

Credits

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

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database