Which versions of praxis-scripts are malicious?

The following npm versions of praxis-scripts are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate praxis-scripts if I installed it?

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

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

Yes — praxis-scripts is associated with the GHSA-37c2-jh79-3hh6, RLMA-2026-01506, RLUA-2026-01809 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 praxis-scripts 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 praxis-scripts (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging praxis-scripts across your stack and pipelines.

Malicious package

praxis-scriptsnpm

Malicious code in praxis-scripts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1362

Immediate action

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

npm uninstall praxis-scripts

What this malware does

The package praxis-scripts 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

99.9.9

Indicators of compromise (SHA-256)

9cf02a0374cd88b4ae46f34a484f0441ea2bfaf3c6799812ea6b4cf4e916cd0c

faf404c8b6477fbe18449cf1f3a818d07e53b7fbc19722389b9c52b364fcf309

f147ac7e867b493ef159ddfdd294c57a1bfbbd8e502037178470c37345ca0628

91178352527de8501af399b20ba6ac36f687598cb4af70cb028a4fd3bb09ab94

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 praxis-scripts (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging praxis-scripts across your stack and pipelines.
If you installed it — respond
Remove praxis-scripts 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 praxis-scripts 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 praxis-scripts 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. praxis-scripts on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-37c2-jh79-3hh6RLMA-2026-01506RLUA-2026-01809

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks praxis-scripts-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