How severe is GHSA-5635-9mvj-r6hp?

GHSA-5635-9mvj-r6hp has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5635-9mvj-r6hp?

GHSA-5635-9mvj-r6hp affects the following packages: vue-backbone (npm). Ecosystems affected: npm.

How do I fix GHSA-5635-9mvj-r6hp?

Update vue-backbone to 0.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5635-9mvj-r6hp is resolved across your whole dependency graph.

How do I detect GHSA-5635-9mvj-r6hp in my npm dependencies?

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

How do I mitigate GHSA-5635-9mvj-r6hp 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-5635-9mvj-r6hp actively exploited in the wild?

No public exploit code has been indexed for GHSA-5635-9mvj-r6hp 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-5635-9mvj-r6hp published, and has it been updated?

GHSA-5635-9mvj-r6hp was published on September 3, 2020 and was last updated on September 30, 2021. 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

CRITICAL severity

Malicious Package in vue-backboneGHSA-5635-9mvj-r6hp

CRITICAL

GHSA-5635-9mvj-r6hp is a critical-severity (CVSS 9.8) vulnerability in vue-backbone. A fix is available for vue-backbone — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 30, 2021 · 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

vue-backbonenpm

685downloads / week

Description

Version 0.1.2 of vue-backbone 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vue-backbone`	≥ 0.1.2&&< 0.1.3	0.1.3`npm install vue-backbone@0.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vue-backbone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vue-backbone to 0.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5635-9mvj-r6hp is resolved across your whole dependency graph.
Workarounds
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.1.2 of `vue-backbone` 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.

O3 Security · Impact-Aware SCA

Is GHSA-5635-9mvj-r6hp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works