# MAL-2026-6255: Malicious code in fork-angular-daterangepicker (npm)


- **Type:** Malicious package
- **Package:** `fork-angular-daterangepicker` (npm)
- **Published:** 21 Jun 2026

## What is MAL-2026-6255?

MAL-2026-6255 is a malicious package in fork-angular-daterangepicker, published on 21 Jun 2026. 

### Official description

package.json declares a preinstall lifecycle hook (`"preinstall": "node index.js"`) that runs index.js on every `npm install`. index.js line 3 hardcodes `https://d8s1eti9io6kqja3sg5gsyqs4aqawhqxg.oast.live/npm-installed` and issues an HTTPS GET to that endpoint at install time. oast.live is an Interactsh / OAST collaborator service; the unique per-subdomain identifier lets whoever generated it confirm — out-of-band — which hosts installed the package, capturing the installer's source IP, DNS resolver, and install timestamp. The package self-describes as a "PoC package for dependency confusion testing" and its name impersonates the legitimate `angular-daterangepicker` package, indicating the beacon's purpose is to verify dependency-confusion hits inside private/internal build environments. Even when framed as a "PoC", running this on a real installer leaks network-position metadata to a third party without consent.

The OpenSSF Package Analysis project identified 'fork-angular-daterangepicker' @ 11.0.0 (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-6255?

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

## Sources

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

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