How severe is GHSA-53jx-4wwh-gcqj?

No CVSS score has been assigned to GHSA-53jx-4wwh-gcqj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-53jx-4wwh-gcqj?

GHSA-53jx-4wwh-gcqj affects the following packages: angular-location-update (npm). Ecosystems affected: npm.

How do I fix GHSA-53jx-4wwh-gcqj?

No patched version of angular-location-update has shipped for GHSA-53jx-4wwh-gcqj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-53jx-4wwh-gcqj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for angular-location-update, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-53jx-4wwh-gcqj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-53jx-4wwh-gcqj actively exploited in the wild?

No public exploit code has been indexed for GHSA-53jx-4wwh-gcqj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-53jx-4wwh-gcqj published, and has it been updated?

GHSA-53jx-4wwh-gcqj was published on September 11, 2020 and was last updated on July 27, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Malicious Package in angular-location-updateGHSA-53jx-4wwh-gcqj

GHSA-53jx-4wwh-gcqj is a security vulnerability in angular-location-update. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 11, 2020

Updated

Jul 27, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 27, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

angular-location-updatenpm

652downloads / week

Description

Version 0.0.3 of angular-location-update contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Recommendation

Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.

Users may consider downgrading to version 0.0.2

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`angular-location-update`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for angular-location-update, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of angular-location-update has shipped for GHSA-53jx-4wwh-gcqj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Version 0.0.3 of `angular-location-update` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation Remove the package from your environment and evaluate your application to determine whether or not user data was compromised. Users may consider downgrading to version 0.0.2

O3 Security · Impact-Aware SCA

Is GHSA-53jx-4wwh-gcqj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works