MAL-2026-5413 Malicious code in @klapp-login-platform/native-sdk (npm)
Malicious package
Published
MAL-2026-5413 is a malicious package: @klapp-login-platform/native-sdk (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-5413/ (Markdown: https://insights.sbomify.com/MAL-2026-5413/index.md)
- Package
- @klapp-login-platform/native-sdk
- Registry
- npm
What is MAL-2026-5413?
MAL-2026-5413 is a malicious package in @klapp-login-platform/native-sdk, published on 9 Jun 2026.
Official description
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.What should I do about MAL-2026-5413?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.