@service-suppliers
The @service-suppliers scope on npm published 15 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 @service-suppliers. 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 @service-suppliers rather than checking a single package name.
- @service-suppliers/fetch-initial-suppliers-watcher-sagaView advisory →
- @service-suppliers/fetch-suppliers-watcher-sagaView advisory →
- @service-suppliers/fetch_initial_suppliers_action_sagaView advisory →
- @service-suppliers/fetch_suppliers_action_sagaView advisory →
- @service-suppliers/fetch_suppliers_country_list_action_sagaView advisory →
- @service-suppliers/reset_country_listView advisory →
- @service-suppliers/select-supplier-watcher-sagaView advisory →
- @service-suppliers/set_country_listView advisory →
- @service-suppliers/set_initial_loadedView advisory →
- @service-suppliers/set_selected_supplierView advisory →
- @service-suppliers/set_selected_supplier_action_sagaView advisory →
- @service-suppliers/set_suppliers_dataView advisory →
- @service-suppliers/set_suppliers_loading_startView advisory →
- @service-suppliers/set_suppliers_loading_stopView advisory →
- @service-suppliers/suppliersView advisory →