Which versions of safe-json-parsex are malicious?

The following npm versions of safe-json-parsex are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate safe-json-parsex if I installed it?

Remove safe-json-parsex from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed safe-json-parsex — how do I know if it already compromised me?

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

Yes — safe-json-parsex is associated with the GHSA-f6jh-hc8p-xpfx, RLMA-2026-01813, RLUA-2026-02037 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 safe-json-parsex 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 safe-json-parsex (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging safe-json-parsex across your stack and pipelines.

Malicious package

safe-json-parsexnpm

Malicious code in safe-json-parsex (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1968

Immediate action

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

npm uninstall safe-json-parsex

What this malware does

The package safe-json-parsex was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

4baa22d0d844650e1fcedcce52b117324903496e0d1399245674b48e4b3ae06d

7c75827c4ff52be2152687faf186ee7a5668e9dd33bd30adfab490a5e2198c30

d48a2ae2f9aebccf52b51df947a590b52d4139fb305afc24e7b21b12b9c58247

6a22bb1d8bd137509478e5613686516a313451ce21b22e115a41edc1443c6e79

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for safe-json-parsex (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging safe-json-parsex across your stack and pipelines.
If you installed it — respond
Remove safe-json-parsex from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If safe-json-parsex 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 safe-json-parsex 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. safe-json-parsex on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f6jh-hc8p-xpfxRLMA-2026-01813RLUA-2026-02037

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks safe-json-parsex-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring