Which versions of remjsonparse are malicious?

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

How do I remediate remjsonparse if I installed it?

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

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

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

Malicious package

remjsonparsePyPI

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

MAL-2026-1290

Immediate action

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

pip uninstall remjsonparse

What this malware does

During import, package starts advanced compromise actions: exfiltrates AWS and git credentials, commands history, security tools in use. After that, the code waits for further commands from C2. The code is also prepared to configure persistence through autostart keys, crontabs or Linux services, as well as to configure new SSH credentials for remote access.

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

Campaign: 2026-03-remjsonparse

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
typosquatting
peristence-autorun
exfiltration-generic
exfiltration-credentials

Malicious versions

7 flagged

0.1.00.1.10.1.20.1.30.1.40.1.60.1.7

Indicators of compromise (SHA-256)

e478d1e016f1d6d6d1cb4a9d23ac45449c22d99aa8e71c88d2f38fae8951f23f

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 remjsonparse (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging remjsonparse across your stack and pipelines.
If you installed it — respond
remjsonparse 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 remjsonparse 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 remjsonparse 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. remjsonparse 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.6, 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-remjsonparse

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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