MAL-2026-6527 Malicious code in @immobiliarelabs/backstage-plugin-gitlab-backend (npm)
Malicious package
Published
MAL-2026-6527 is a malicious package: @immobiliarelabs/backstage-plugin-gitlab-backend (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-6527/ (Markdown: https://insights.sbomify.com/MAL-2026-6527/index.md)
- Package
- @immobiliarelabs/backstage-plugin-gitlab-backend
- Registry
- npm
What is MAL-2026-6527?
MAL-2026-6527 is a malicious package in @immobiliarelabs/backstage-plugin-gitlab-backend, published on 26 Jun 2026.
Official description
The package ships a binding.gyp at the package root whose contents use GYP command-expansion syntax (
<!(...)) inside its targets/sources fields. npm implicitly runs node-gyp rebuild whenever a binding.gyp is present — even with no declared install/postinstall script — and GYP evaluates <!(...) as a shell command during the configure step. The result is that npm install @immobiliarelabs/[email protected] causes an embedded shell command to execute on the installer machine without any explicit lifecycle hook. The package presents itself as a Backstage backend plugin (pure TypeScript/JavaScript), which has no legitimate need to ship a native-addon build descriptor; the binding.gyp's purpose is to run the embedded command at install time. the analysis of this artifact tripped the provider's malware-output safety filter, which corroborates the malicious shape of the contents. Treat as install-time remote code execution: the harmful path is automatic on a default npm install.What should I do about MAL-2026-6527?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.