@client-web-next
The @client-web-next scope on npm published 22 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 @client-web-next. 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 @client-web-next rather than checking a single package name.
- @client-web-next/ab-landing-formView advisory →
- @client-web-next/ab-testsView advisory →
- @client-web-next/adaptiveView advisory →
- @client-web-next/analyticsView advisory →
- @client-web-next/api-metricsView advisory →
- @client-web-next/cmsView advisory →
- @client-web-next/env-utilView advisory →
- @client-web-next/event-bus-listenerView advisory →
- @client-web-next/feature-flagsView advisory →
- @client-web-next/footerView advisory →
- @client-web-next/iconsView advisory →
- @client-web-next/loggerView advisory →
- @client-web-next/navigation-linkView advisory →
- @client-web-next/origination-microfrontView advisory →
- @client-web-next/providersView advisory →
- @client-web-next/tarjeta-buttonView advisory →
- @client-web-next/timerView advisory →
- @client-web-next/transfer-stateView advisory →
- @client-web-next/ua-parserView advisory →
- @client-web-next/uiView advisory →
- @client-web-next/ui-businessView advisory →
- @client-web-next/utilsView advisory →