@access-risk/browser-remedy-reactnpm
Advisory published Updated
@access-risk/browser-remedy-react is a confirmed malicious npm package (MAL-2026-5520) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @access-risk/browser-remedy-react (npm)
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
Search your lockfiles and build artifacts for @access-risk/browser-remedy-react (2 malicious versions).
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 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
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.