@klapp-login-platform/native-sdknpm
Malicious code in @klapp-login-platform/native-sdk (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, the package's preinstall lifecycle hook runs node index.js, which collects installer-side identifiers — os.hostname(), os.userInfo().username, __dirname, process.cwd(), and the package name — and exfiltrates them through two channels. First, the JSON payload is hex-encoded into DNS labels and resolved under *.d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live, an out-of-band collector. Second, the same JSON is POSTed to a bare IP http://172.201.213.59:9090/c. Neither destination matches any documented vendor SDK endpoint. The package metadata reinforces malicious intent: the scope @klapp-login-platform resembles an internal namespace, the description is security research, and the version 99.0.2 is inflated to win dependency-confusion resolution against a private package. Installing the package immediately leaks host identity to attacker-controlled infrastructure.
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 @klapp-login-platform/native-sdk (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @klapp-login-platform/native-sdk across your stack and pipelines.
If you installed it — respond
@klapp-login-platform/native-sdk 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 @klapp-login-platform/native-sdk 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 @klapp-login-platform/native-sdk 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 @klapp-login-platform/native-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.