MAL-2026-5422 Malicious code in @nstrlabs/shared-components (npm)
Malicious package
Published
MAL-2026-5422 is a malicious package: @nstrlabs/shared-components (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-5422/ (Markdown: https://insights.sbomify.com/MAL-2026-5422/index.md)
- Package
- @nstrlabs/shared-components
- Registry
- npm
What is MAL-2026-5422?
MAL-2026-5422 is a malicious package in @nstrlabs/shared-components, published on 9 Jun 2026.
Official description
On
npm install, the package's preinstall script runs index.js, which collects host identifiers (os.hostname(), os.userInfo().username, __dirname, process.cwd(), package name) and ships them to two attacker-controlled destinations: (1) a hex-encoded DNS subdomain query against *.d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (Interactsh-style out-of-band exfiltration), and (2) an HTTP POST of the same JSON payload to bare IP http://172.201.213.59:9090/c. The package is published under @nstrlabs/shared-components at version 99.0.0 with description security research — a high semver against a generic scoped name consistent with a dependency-confusion attack targeting an internal nstrlabs namespace. There is no legitimate library functionality; the preinstall beacon is the package's only effect.What should I do about MAL-2026-5422?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.