Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@immobiliarelabs/backstage-plugin-gitlabnpm

Malicious code in @immobiliarelabs/backstage-plugin-gitlab (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6526
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @immobiliarelabs/backstage-plugin-gitlab

What this malware does

The package ships a binding.gyp at the package root whose targets/sources fields contain GYP command-expansion syntax (<!(...)) at line 6. npm implicitly invokes node-gyp rebuild whenever a binding.gyp is present, even without any declared install/postinstall script, and node-gyp/GYP evaluates <!(...) as a shell command during the configure step. This causes the embedded command to execute on every npm install of this package as a transitive or direct dependency. The package presents itself as a Backstage GitLab plugin (a pure TypeScript/React frontend plugin), a category that has no legitimate need to build a native addon — and consistent with that, no C/C++ source files are shipped alongside binding.gyp, so the file's only effect is to run the embedded shell command at install time. The traced content of this install-time code path was withheld by the upstream model's malware-output safety filter, which is itself a corroborating signal that the executed content reads as operational malware rather than benign build logic.

Malicious versions

7 flagged
1.0.12.1.23.0.34.0.25.2.16.13.17.0.2

Indicators of compromise (SHA-256)

00eb86df154a9532085ad285ee63cd4c4f9a95a6fe983b9930cd059dfb4cb3f5
1f15945dc37e8e88a581ff3869d6f2c2efa39eddcbbc5d61b82aa05ff10c0e28
3156ada55f6dcb5e429a184f246f6e60bb77a31c84231961e0803e76cafced0b
85667e8ad429ae8bd36193c38af3b567789bdefb047aee9669fa9bd201bfcfc9
8dcf811afd941947d8357bb6aa5c85d523861abd115900b5f151a0806f9da3e1
bd3ae7900c4da339c927696cbb58db4c1d920641adfea39ddf98f355eb2188ca
ddefa4518a49e0dfd8d005fb64a893a86029a2f836c7b9d60813e1710f2d6141

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @immobiliarelabs/backstage-plugin-gitlab (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @immobiliarelabs/backstage-plugin-gitlab across your stack and pipelines.

  2. If you installed it — respond

    Remove @immobiliarelabs/backstage-plugin-gitlab from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @immobiliarelabs/backstage-plugin-gitlab was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @immobiliarelabs/backstage-plugin-gitlab before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @immobiliarelabs/backstage-plugin-gitlab on npm has been identified as a malicious package (versions 1.0.1, 2.1.2, 3.0.3, 4.0.2, 5.2.1, 6.13.1, 7.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007624IN-MAL-2026-007623IN-MAL-2026-007612IN-MAL-2026-007622IN-MAL-2026-007610IN-MAL-2026-007609IN-MAL-2026-007625

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @immobiliarelabs/backstage-plugin-gitlab-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.