@access-risk/browser-remedy-reactnpm
Malicious code in @access-risk/browser-remedy-react (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, postinstall.js executes automatically and collects host identity and environment details using os.hostname(), process.cwd(), and filesystem reads, base64-encodes the data via Buffer.from(...).toString('base64'), and exfiltrates it through both DNS lookups (require('dns')) and HTTPS requests (require('https')). The dual-channel base64 exfiltration shape (DNS tunneling plus HTTPS POST) combined with collection of system identifiers is the canonical install-time data-theft fingerprint and provides direct attacker benefit: any machine running npm install for this package leaks identifying information to an external destination automatically, before the user has reviewed any package code.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @access-risk/browser-remedy-react (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @access-risk/browser-remedy-react across your stack and pipelines.
If you installed it — respond
@access-risk/browser-remedy-react 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 @access-risk/browser-remedy-react 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 @access-risk/browser-remedy-react 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @access-risk/browser-remedy-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.