Which versions of xrblocks-remote-control are malicious?

The following npm versions of xrblocks-remote-control are flagged malicious: 22.0.0. Treat any of these as compromised.

How do I remediate xrblocks-remote-control if I installed it?

xrblocks-remote-control establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed xrblocks-remote-control — how do I know if it already compromised me?

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

Yes — xrblocks-remote-control is associated with the IN-MAL-2026-007642, GHSA-24xr-qqmw-jvvf 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 xrblocks-remote-control 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 xrblocks-remote-control (version 22.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xrblocks-remote-control across your stack and pipelines.

Malicious package

xrblocks-remote-controlnpm

xrblocks-remote-control is a confirmed malicious npm package (MAL-2026-6530) that opens a backdoor for remote access (malicious version 22.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xrblocks-remote-control (npm)

MAL-2026-6530

Immediate action

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

npm uninstall xrblocks-remote-control

What this malware does

Package xrblocks-remote-control ships a bin script that, when invoked (including via npx or unintended resolution against the xrblocks name), POSTs the basename of process.env.INIT_CWD (the installer's project directory name) plus a timestamp to a hardcoded external callback at https://deepbounty.dd06-dev.fr/cb/46b252ec-a089-4f22-8b5e-5cee945106dc. The package provides no advertised functionality — package.json self-describes as a 'Security PoC for Bug Bounty' and no main module is shipped; the bin's sole effect is the outbound beacon. The package name targets Google's xrblocks namespace as a dependency-confusion / typosquat probe. Regardless of whether the operator is a bug-bounty researcher, installers and build systems that resolve this package have a project identifier transmitted to a third-party host without consent.

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

22.0.0

Indicators of compromise (SHA-256)

6e20199ccf4c5557bf9d6bd0f17f0f74b47aa54389f22247523fb9145ef29def

de2e8b166cf80d83908ce089f14e154200213428f88c8949a64e946aa8c69185

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xrblocks-remote-control (version 22.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xrblocks-remote-control across your stack and pipelines.
If you installed it — respond
xrblocks-remote-control establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If xrblocks-remote-control 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 xrblocks-remote-control 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. xrblocks-remote-control on npm has been identified as a malicious package (version 22.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007642GHSA-24xr-qqmw-jvvf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks xrblocks-remote-control-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database