osep-api-hub-service-client-v1npm
Malicious code in osep-api-hub-service-client-v1 (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares "preinstall": "node index.js", causing index.js to run automatically on npm install. index.js collects host identifiers — os.hostname(), os.userInfo() (username/uid/gid/shell), os.homedir(), process.platform, process.arch, process.cwd() — and additionally shells out via child_process to whoami and id. The collected JSON is POSTed to the hardcoded URL https://0pqbxi1hplohnif3fa7tyc1at1zsnobd.oastify.com/detox56, a Burp Collaborator (oastify.com) subdomain controlled by whoever published the package. The package name mimics an internal-sounding scoped client and ships with empty author/description metadata, consistent with a dependency-confusion attack targeting a private package namespace. Any developer or CI system that installs this package immediately leaks host and user identity to the attacker's Collaborator endpoint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for osep-api-hub-service-client-v1 (version 10.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging osep-api-hub-service-client-v1 across your stack and pipelines.
If you installed it — respond
osep-api-hub-service-client-v1 is a typosquat — you almost certainly intended a legitimately-named package. Remove osep-api-hub-service-client-v1, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If osep-api-hub-service-client-v1 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 osep-api-hub-service-client-v1 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 osep-api-hub-service-client-v1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.