Malicious Package in slush-fullstack-frameworkGHSA-4j54-mmmv-hjpm
GHSA-4j54-mmmv-hjpm is a security vulnerability in slush-fullstack-framework. No vendor fix is recorded yet; mitigation options are listed below.
Real-World Exposure
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.
slush-fullstack-frameworknpmDescription
Version 0.9.2 of slush-fullstack-framework contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=
Recommendation
Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.
Users may consider downgrading to version 0.9.1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | slush-fullstack-framework | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slush-fullstack-framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of slush-fullstack-framework has shipped for GHSA-4j54-mmmv-hjpm 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
Is GHSA-4j54-mmmv-hjpm in your dependencies?
Find it across npm, including transitive dependencies.