@marketfront
The @marketfront scope on npm published 25 malicious packages. See the full package list, affected versions, and how to check whether your dependency tree pulled any of them in.
What to do if you depend on any of these
Every package below was published as malicious under @marketfront. Treat any machine that installed one as compromised: remove the package and its lockfile entry, rotate every credential the build or runtime could reach (registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values) from a known-clean machine, and audit for unexpected outbound activity.
Because the packages share a publisher scope, a project that pulled in one has an elevated chance of having pulled in others. Search your lockfiles for @marketfront rather than checking a single package name.
- @marketfront/actualordersnippetpopupView advisory →
- @marketfront/advertisingdevtoolView advisory →
- @marketfront/bannerpopupView advisory →
- @marketfront/baobabtechView advisory →
- @marketfront/basemarkettemplateView advisory →
- @marketfront/blenderdevtoolView advisory →
- @marketfront/captchaserviceView advisory →
- @marketfront/changefilterView advisory →
- @marketfront/commonecommerceView advisory →
- @marketfront/customdealsfeedView advisory →
- @marketfront/designsystemdevtoolView advisory →
- @marketfront/devtoolsloaderView advisory →
- @marketfront/digitalherobannercarouselView advisory →
- @marketfront/dynamicpageparamsView advisory →
- @marketfront/errorcounterView advisory →
- @marketfront/fashiononboardingpopupView advisory →
- @marketfront/fingerprintView advisory →
- @marketfront/footerView advisory →
- @marketfront/gotoauthpopupView advisory →
- @marketfront/headerView advisory →
- @marketfront/infopopupView advisory →
- @marketfront/livestreampreviewpopupView advisory →
- @marketfront/madvpopupView advisory →
- @marketfront/mychatspreloaderView advisory →
- @marketfront/navbarView advisory →