What does the testjsonn2 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 'testjsonn2' @ 0.1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of testjsonn2 are malicious?

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

How do I remediate testjsonn2 if I installed it?

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

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

Yes — testjsonn2 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 testjsonn2 across my projects, lockfiles, and CI pipelines?

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

Malicious package

testjsonn2PyPI

Advisory published Jul 21, 2024Updated Dec 12, 2025

testjsonn2 is a confirmed malicious PyPI package (MAL-2024-7840) 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 testjsonn2 (PyPI)

MAL-2024-7840

Immediate action

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

pip uninstall testjsonn2

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 'testjsonn2' @ 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)

5805b7fd85e9ce8cc9ba939125ed7edb16256af6a67d1666522b4b764c281b11

b10de3dc760a8fef01b1ee9366131ba838e61ce1107f4780833645658a932d9f

0d75d52ae07c9c9e2e6b773f2806c66631dd764da793bac0559e65bc4d0e7f66

9ca822b55fdf080d2d92e43e0eef7c0e47ec221c7b4236baf304ef15f52e405f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for testjsonn2 (version 0.1).
If you installed it — respond
testjsonn2 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 testjsonn2 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. testjsonn2 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 testjsonn2-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