@service-suppliers/fetch_suppliers_action_saganpm
Malicious code in @service-suppliers/fetch_suppliers_action_saga (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The postinstall script (scripts/postinstall.js) performs three independent installer-harm actions on npm install. (1) It enumerates process.env for credential-shaped keys (npm_token, npm_config_authtoken, github_token, aws_access_key_id, aws_secret_access_key, aws_session_token, artifactory_token, nexus_token, node_auth_token, npm_config__auth, etc.), reads ~/.npmrc, /etc/npmrc,./.npmrc, and../.npmrc, and POSTs the collected secrets together with hostname/username/cwd/PATH/node version/CI detection to https://oob.moika.tech/report with a hardcoded X-Secret header. (2) It GETs https://oob.moika.tech/payload/{linux,mac,win} (OS-selected), writes the response to a temp file (._service-suppliers_init.sh or .bat), chmods 0755, and spawns it via /bin/sh or cmd.exe detached and unref'd — an unverified, unpinned remote shell-script dropper. (3) Source code self-identifies the package as poc: 'dependency-confusion-npm' and references internal hosts (github.service-suppliers.io, jira.service-suppliers.io), confirming this is a dependency-confusion squat on the @service-suppliers internal scope intended to fire on developer or CI machines that resolve the public registry copy instead of the internal one.
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/fetch_suppliers_action_saga (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/fetch_suppliers_action_saga across your stack and pipelines.
If you installed it — respond
@service-suppliers/fetch_suppliers_action_saga 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/fetch_suppliers_action_saga 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/fetch_suppliers_action_saga 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/fetch_suppliers_action_saga-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.