# MAL-2026-5344: Malicious code in @bancolonbia/menu-filter-widget-web (npm)


- **Type:** Malicious package
- **Package:** `@bancolonbia/menu-filter-widget-web` (npm)
- **Published:** 9 Jun 2026

## What is MAL-2026-5344?

MAL-2026-5344 is a malicious package in @bancolonbia/menu-filter-widget-web, published on 9 Jun 2026. 

### Official description

package.json declares `scripts.postinstall: node./callback.js`, which fires automatically on `npm install`. callback.js reads the installer's hostname and transmits it to a hardcoded Burp Collaborator domain (`3y294ed4dfq501wnmdvbakcnwe25qvek.oastify.com`) via two channels: an HTTPS GET to `/<token>/<encodeURIComponent(host)>` and a DNS lookup against a subdomain encoding the same token + hostname. The package self-describes as an "authorized security research PoC" but is published under the `@bancolonbia` scope (a likely typosquat of the Bancolombia corporate namespace), matching the classic dependency-confusion shape: a private-looking scoped name registered publicly so a misconfigured internal build resolves to this package and beacons victim identity to the researcher/attacker. Whether or not the operator is authorized by Bancolombia, any third party who installs this package has their hostname exfiltrated to an attacker-controlled Collaborator endpoint without consent.

The OpenSSF Package Analysis project identified '@bancolonbia/menu-filter-widget-web' @ 0.0.1 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-5344?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5344 is a malicious package: @bancolonbia/menu-filter-widget-web (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-5344/ (Markdown: https://insights.sbomify.com/MAL-2026-5344/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5344

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5344/
Summaries are generated and may contain mistakes; the official description above is the record.