Which versions of ingularjs are malicious?

The following npm versions of ingularjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate ingularjs if I installed it?

Remove ingularjs 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 ingularjs — how do I know if it already compromised me?

If ingularjs 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 ingularjs part of a known attack campaign?

Yes — ingularjs is associated with the RLMA-2026-05115, RLUA-2026-06283 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 ingularjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ingularjs (3 malicious versions).

Malicious package

ingularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ingularjs is a confirmed malicious npm package (MAL-2026-7301) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ingularjs (npm)

MAL-2026-7301

Immediate action

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

npm uninstall ingularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

1a000c33c6e2ab4aaace56cf1547ecdd00d9e709ce732130d411f32bcf95ffbc

3c4b23eb7ff17db9d1ef7c93b69c3d88174e2ad5f738f44c94ae3c56dc1f2d04

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ingularjs (3 malicious versions).
If you installed it — respond
Remove ingularjs 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 ingularjs 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. ingularjs on npm has been identified as a malicious package (versions 1.1.2, 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05115RLUA-2026-06283

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ingularjs-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