@awazevr/mfe-common.contexts.guest-authnpm
Advisory published Updated
@awazevr/mfe-common.contexts.guest-auth is a confirmed malicious npm package (MAL-2026-20277) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @awazevr/mfe-common.contexts.guest-auth (npm)
What this malware does
Package @awazevr/mfe-common.contexts.guest-auth publishes to the unregistered public-registry scope @awazevr, which is used by a third-party organization for private internal packages. The package.json declares a postinstall script that executes shell commands (whoami, hostname) on every install, prefixed with an echoed banner identifying the artifact as a dependency-confusion proof-of-concept. Any build system that resolves this scope from the public npm registry (for example, a CI job misconfigured to fetch an internal @awazevr dependency without a scoped-registry pin) auto-executes the author's shell code on install. The current payload only prints local host identifiers rather than exfiltrating or fetching remote code, but the install-time arbitrary command execution path and the scope-shadowing mechanism are fully functional, and the same vector delivers whatever commands subsequent versions place in the postinstall script. Self-identification as bug-bounty research does not change the installer-facing behavior: the lifecycle hook runs attacker-authored commands on the installer host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @awazevr/mfe-common.contexts.guest-auth (version 1.0.0).
If you installed it — respond
@awazevr/mfe-common.contexts.guest-auth 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 @awazevr/mfe-common.contexts.guest-auth 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 @awazevr/mfe-common.contexts.guest-auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.