# MAL-2026-6547: Malicious code in react-editable-calendar (npm)


- **Type:** Malicious package
- **Package:** `react-editable-calendar` (npm)
- **Published:** 27 Jun 2026

## What is MAL-2026-6547?

MAL-2026-6547 is a malicious package in react-editable-calendar, published on 27 Jun 2026. 

### Official description

package.json declares a preinstall hook `node src/utils/index.d.js`, but the published tarball's `files` whitelist ships only `dist/`, `README.md`, and `LICENSE` — `src/utils/index.d.js` is not present, so `npm install` will fail with ENOENT before any package code executes. No exfiltration, dropper, or attacker-controlled network destination is reachable in the shipped artifact. Separately, the published name `react-editable-calendar` does not match the library's documented identity (`schedulaforge`, exporting a `SchedulaForge` class) and the package contains no React-specific code; the chosen name appears positioned to attract developers searching for a React calendar component. Together these signals — a dangling preinstall pointer to a non-shipped script in a headless library, plus a name/identity mismatch — are atypical enough to warrant human review of the maintainer's intent, but the artifact as published does not harm installers.

The OpenSSF Package Analysis project identified 'react-editable-calendar' @ 0.1.7 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

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

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

## Sources

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

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