# MAL-2026-13783: Malicious code in bcnfjndwbkf2 (npm)


- **Type:** Malicious package
- **Package:** `bcnfjndwbkf2` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-7cv8-7v66-c3mh

## What is MAL-2026-13783?

MAL-2026-13783 is a malicious package in bcnfjndwbkf2, published on 12 Aug 2026. 

### Official description

The package contains only index.html and declares main: 'index.html' with no scripts, no bin, and no JavaScript library surface. The HTML mimics a Cloudflare 'Just a moment...' interstitial and, after a 1s timeout, runs obfuscator.io-style code that reconstructs a target URL from a rotated base64 string array (visible fragments include 'gin.microc' and '/') and calls window.location.replace() to it, forwarding current URL search params. Because main points at an HTML file, the package cannot be require()'d or import()'d, has no lifecycle hooks, and does not execute code on npm install. Installing or depending on this package does not run the redirector against the installer — the content only affects browser visitors who fetch the HTML via an npm CDN mirror (unpkg/jsdelivr). This is npm-as-static-host abuse for a browser-side redirect page rather than a supply-chain attack against installers.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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-13783 is a malicious package: bcnfjndwbkf2 (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-13783/ (Markdown: https://insights.sbomify.com/MAL-2026-13783/index.md)
```

## Sources

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

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