MAL-2026-5863 Malicious code in @ts-internal/shared-lib (npm)
Malicious package
Published
MAL-2026-5863 is a malicious package: @ts-internal/shared-lib (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-5863/ (Markdown: https://insights.sbomify.com/MAL-2026-5863/index.md)
- Package
- @ts-internal/shared-lib
- Registry
- npm
What is MAL-2026-5863?
MAL-2026-5863 is a malicious package in @ts-internal/shared-lib, published on 16 Jun 2026.
Official description
The package squats the internal-looking scope @ts-internal/shared-lib on the public npm registry and runs a network beacon both during install (preinstall and postinstall hooks invoke
node lifecycle.js) and on module load (index.js calls require('./beacon').beacon('require')). beacon.js collects os.hostname(), os.userInfo().username, process.cwd(), os.platform(), and the package name/version, hex-encodes the blob, and transmits it via DNS lookup and HTTPS GET to d8oa6q03t3o2ksbjirogwxiwiyhp6e57o.oast.site (an interactsh OAST collector) and npm-dc-seek-1781572474.testingboxes.com. Any build that misresolves this name to the public registry will silently leak identifying host metadata to two third-party endpoints. The README self-describes the package as a dependency-confusion proof-of-concept, but installers cannot consent and cannot verify researcher authorization; the squat-plus-beacon mechanism is the attack regardless of stated intent.What should I do about MAL-2026-5863?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.