Which versions of mbt are malicious?

The following npm versions of mbt are flagged malicious: 1.2.48. Treat any of these as compromised.

How do I remediate mbt if I installed it?

mbt is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed mbt — how do I know if it already compromised me?

If mbt was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find mbt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mbt (version 1.2.48).

Malicious package

mbtnpm

Advisory published Apr 29, 2026Updated May 1, 2026

mbt is a confirmed malicious npm package (MAL-2026-3179) that steals credentials and exfiltrates sensitive data (malicious version 1.2.48). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mbt (npm)

MAL-2026-3179

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall mbt

What this malware does

Supply chain compromise of legitimate SAP packages published by threat actor "[email protected]" impersonating SAP toolchain maintainers. All four compromised packages share the same fingerprint: setup.mjs (4.4 KB) and execution.js (11.1 MB) bundled in the tarball, with a preinstall hook of "node setup.mjs". Notably, setup.mjs is explicitly excluded from the package.json 'files' allowlist yet is still shipped in the tarball — a manifest evasion technique intended to hide the malicious file from allowlist inspection while still executing it on install. execution.js (11.1 MB) is anomalously large for these packages and is consistent with an embedded payload or exfiltration binary. Packages were published 2026-04-29T09:55Z.

mbt (SAP Multi-Target Application Build Tool) is a high-impact CLI tool used in SAP CI/CD pipelines to compile and package MTA projects. Its privileged position in build environments makes it a valuable target for credential and token exfiltration.

The package mbt was found to contain malicious code.

Malicious versions

1 flagged

1.2.48

Indicators of compromise (SHA-256)

62b15ba37c3071554cc586ba582589ad51abba89e1be51e993afdf933a18c8b1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for mbt (version 1.2.48).
If you installed it — respond
mbt is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If mbt was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mbt on npm has been identified as a malicious package (version 1.2.48 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks mbt-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database