Which versions of @mep-exp/api-tools are malicious?

The following npm versions of @mep-exp/api-tools are flagged malicious: 2.0.3. Treat any of these as compromised.

How do I remediate @mep-exp/api-tools if I installed it?

@mep-exp/api-tools establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @mep-exp/api-tools — how do I know if it already compromised me?

If @mep-exp/api-tools 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.

Is @mep-exp/api-tools part of a known attack campaign?

Yes — @mep-exp/api-tools is associated with the IN-MAL-2026-007054 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @mep-exp/api-tools across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mep-exp/api-tools (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mep-exp/api-tools across your stack and pipelines.

Malicious package

@mep-exp/api-toolsnpm

Malicious code in @mep-exp/api-tools (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6183

Immediate action

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

npm uninstall @mep-exp/api-tools

What this malware does

preinstall.js, registered as scripts.preinstall and also required from the main module and every bin entry, collects os.hostname(), os.userInfo().username, os.platform(), process.cwd(), and a timestamp and POSTs them as JSON to https://webhook.site/1ba25769-0f80-4429-a7d2-409af5fa5adc. The request runs unconditionally during npm install (preinstall lifecycle) and on every require/CLI invocation, with errors silently swallowed. The package scope (@mep-exp) and bin names (mesh-swagger-cli, mesh-exp-entitlements, mesh-exp-routes, mesh-exp-api-clients, etc.) impersonate an internal Westpac 'MEP Experience Platform' toolchain, and the exfil payload includes a note: "Westpac CT" marker — consistent with a dependency-confusion attack against that organization's internal namespace published on public npm. The package provides no legitimate functionality beyond the beacon.

Malicious versions

1 flagged

2.0.3

Indicators of compromise (SHA-256)

322089c1a58142401c82621aa778cdb7221086196cce6c879a703625b7013555

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mep-exp/api-tools (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mep-exp/api-tools across your stack and pipelines.
If you installed it — respond
@mep-exp/api-tools establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @mep-exp/api-tools 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.
How O3 protects you
O3 blocks @mep-exp/api-tools 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. @mep-exp/api-tools on npm has been identified as a malicious package (version 2.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007054

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @mep-exp/api-tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring