MAL-2026-5420 Malicious code in @nstrlabs/ixel (npm)
Malicious package
Published
MAL-2026-5420 is a malicious package: @nstrlabs/ixel (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-5420/ (Markdown: https://insights.sbomify.com/MAL-2026-5420/index.md)
- Package
- @nstrlabs/ixel
- Registry
- npm
What is MAL-2026-5420?
MAL-2026-5420 is a malicious package in @nstrlabs/ixel, published on 9 Jun 2026.
Official description
On
npm install, the package runs node index.js via a preinstall lifecycle hook (declared as "preinstall": "node index.js || true" so failures are silenced). index.js collects os.hostname(), os.userInfo().username, __dirname, and process.cwd() and exfiltrates them two ways: (1) a hex-encoded subdomain DNS query against *.d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (interactsh-style out-of-band beacon), and (2) an HTTP POST of a JSON blob to the hardcoded bare IP http://172.201.213.59:9090/c. Errors are swallowed via || true, try/catch, and a no-op HTTP error handler so the install appears to succeed. The package is published under the @nstrlabs scope at version 99.0.0 with description 'security research' — the canonical dependency-confusion recon shape, where a high version is published to a public registry to override an internal-scope package and beacon any host that resolves it. The package has no legitimate functionality; its only effect on install is the host-metadata beacon.What should I do about MAL-2026-5420?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.