@service-suppliers/set_selected_suppliernpm
Malicious code in @service-suppliers/set_selected_supplier (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The postinstall hook in scripts/postinstall.js performs two independently-blocking actions on every npm install. First, it scrapes installer-side secrets — iterating process.env for credential-shaped keys (npm_token, github_token, aws_access_key_id, aws_secret_access_key, artifactory_token, nexus_token, NODE_AUTH_TOKEN, npm_config__auth), reading ~/.npmrc, /etc/npmrc, and the CWD.npmrc, plus hostname/user/cwd/PATH — and POSTs the bundle to https://oob.moika.tech/report with an X-Secret header. Second, it fetches an OS-specific shell payload from https://oob.moika.tech/payload/{linux|mac|win}, writes it to a hidden temp file (._service-suppliers_init.sh /.bat), chmods 0755, and spawns it detached via /bin/sh or cmd.exe with no hash or signature verification. The package self-identifies in its exfil report as a 'dependency-confusion-npm' PoC and uses the @service-suppliers scope with placeholder homepage/repo URLs (github.service-suppliers.io) consistent with impersonating an internal scope to hijack private name resolution. Regardless of the 'authorized testing' label, anyone who installs this from public npm has their npm/GitHub/AWS/Artifactory tokens harvested and arbitrary attacker-controlled code executed on their machine.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @service-suppliers/set_selected_supplier (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @service-suppliers/set_selected_supplier across your stack and pipelines.
If you installed it — respond
@service-suppliers/set_selected_supplier is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @service-suppliers/set_selected_supplier was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @service-suppliers/set_selected_supplier before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @service-suppliers/set_selected_supplier-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.