Which versions of @rexorg/config are malicious?

The following npm versions of @rexorg/config are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @rexorg/config if I installed it?

Remove @rexorg/config 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 @rexorg/config — how do I know if it already compromised me?

If @rexorg/config 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 @rexorg/config part of a known attack campaign?

Yes — @rexorg/config is associated with the GHSA-xpmv-42gw-w7wc, RLMA-2026-01864 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 @rexorg/config 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 @rexorg/config (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rexorg/config across your stack and pipelines.

Malicious package

@rexorg/confignpm

Malicious code in @rexorg/config (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2217

Immediate action

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

npm uninstall @rexorg/config

What this malware does

The package @rexorg/config 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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

d3c7f7c6129d24b5a4ee9f95be492524854c16742b8b538f33972fea399c64f5

4a10d1a86c535852318ad135eca1236f436ad942657df6107d1e1e8a117faf42

3d03d368ca501ed2821633187b2fdcbda3bc62283971b181f4bbdd8dfc18aff0

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

Campaign

GHSA-xpmv-42gw-w7wcRLMA-2026-01864

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @rexorg/config-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