MAL-2026-20277: Malicious code in @awazevr/mfe-common.contexts.guest-auth (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (e2e3bcba4ce94634e40d0c13a284e37e60b2edf4c84479e4e8aa7347a417bc26) 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.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this package?
Build systems or developer environments that resolve the @awazevr scope from the public npm registry are exposed, particularly where an internal @awazevr dependency is requested without a scoped-registry pin. The risk is dependency confusion: the public package can be selected in place of an expected private internal package.
What must happen for the code to run?
The package must be installed by npm in an environment that runs lifecycle scripts. Its postinstall script executes shell commands automatically during installation.
Are systems affected if they do not install packages from the public registry for this scope?
The described dependency-confusion path depends on resolving @awazevr packages from the public npm registry. A scoped registry configuration that reliably directs this scope to the intended private registry prevents that public-resolution path.
What can be done while patching or remediating registry configuration?
Pin the @awazevr scope to the intended private registry and prevent public npm resolution for that scope. Review CI jobs and other build configurations that may install internal dependencies without that scoped-registry setting.
How can teams determine whether the payload executed?
Check installation and CI logs for the package and for its postinstall output, which includes an echoed banner and runs whoami and hostname. The provided data describes the current payload as printing local host identifiers rather than exfiltrating data or retrieving remote code.