Which versions of @angulaar/core are malicious?

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

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

Remove @angulaar/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

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

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

Malicious package

@angulaar/corenpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

@angulaar/core is a confirmed malicious npm package (MAL-2026-17537) that executes malicious code on install (malicious version 22.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @angulaar/core (npm)

MAL-2026-17537

Immediate action

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

npm uninstall @angulaar/core

What this malware does

The package's package.json defines a postinstall lifecycle script that fetches a JavaScript file from a non-publisher host (gitflic.ru, proxied via web.archive.org, at the path /project/hellscripter/install-scripts/blob/raw?file=node.js) and pipes the response directly into node, executing arbitrary remote code on the installer's machine during npm install. The fetched code is unpinned, unverified, and controlled by a third-party account unrelated to the Angular project. The package name @angulaar/core resembles @angular/core, increasing the likelihood of accidental installation.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

42861c7641349d2f58380e4f81b13ad9738dd254f224e9f7f239d9cf940cf792

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @angulaar/core (version 22.2.1).
If you installed it — respond
Remove @angulaar/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @angulaar/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. @angulaar/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-020998

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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