Which versions of @ra-ide/logix-frontend are malicious?

The following npm versions of @ra-ide/logix-frontend are flagged malicious: 141.3.1. Treat any of these as compromised.

How do I remediate @ra-ide/logix-frontend if I installed it?

Remove @ra-ide/logix-frontend 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 @ra-ide/logix-frontend — how do I know if it already compromised me?

If @ra-ide/logix-frontend 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.

How do I find @ra-ide/logix-frontend across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ra-ide/logix-frontend (version 141.3.1).

Part of a larger attack: @ra-ide published 9 malicious packages. See the full campaign →

Malicious package

@ra-ide/logix-frontendnpm

Advisory published Nov 20, 2025Updated Nov 24, 2025

@ra-ide/logix-frontend is a confirmed malicious npm package (MAL-2025-190593) that executes malicious code on install (malicious version 141.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ra-ide/logix-frontend (npm)

MAL-2025-190593

Immediate action

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

npm uninstall @ra-ide/logix-frontend

What this malware does

The package @ra-ide/logix-frontend was found to contain malicious code.

The OpenSSF Package Analysis project identified '@ra-ide/logix-frontend' @ 141.3.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

141.3.1

Indicators of compromise (SHA-256)

3fc5d77c24abc572b5b9db101acaf281c49c9ec3dd3dd9e2f3e9b2ed72d9c428

1d0e9dbec30cd8b41d8e4b83527959c2b2e24abd51fcdd958e18ead57f3b4bf0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @ra-ide/logix-frontend (version 141.3.1).
If you installed it — respond
Remove @ra-ide/logix-frontend 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 @ra-ide/logix-frontend 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. @ra-ide/logix-frontend on npm has been identified as a malicious package (version 141.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @ra-ide/logix-frontend-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

Explore

All malware advisories How O3 detects malware Vulnerability database