Which versions of ing-ideal-acquiring-shared are malicious?

The following npm versions of ing-ideal-acquiring-shared are flagged malicious: 15.1.26. Treat any of these as compromised.

How do I remediate ing-ideal-acquiring-shared if I installed it?

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

If ing-ideal-acquiring-shared 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 ing-ideal-acquiring-shared part of a known attack campaign?

Yes — ing-ideal-acquiring-shared is associated with the RLMA-2025-05814 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 ing-ideal-acquiring-shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ing-ideal-acquiring-shared (version 15.1.26).

Malicious package

ing-ideal-acquiring-sharednpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

ing-ideal-acquiring-shared is a confirmed malicious npm package (MAL-2025-191575) that executes malicious code on install (malicious version 15.1.26). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ing-ideal-acquiring-shared (npm)

MAL-2025-191575

Immediate action

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

npm uninstall ing-ideal-acquiring-shared

What this malware does

The package ing-ideal-acquiring-shared was found to contain malicious code.

Malicious versions

1 flagged

15.1.26

Indicators of compromise (SHA-256)

23fa915a2011cb72753166297a012e5818cafd1a583cbf8c4bfd5fd3341da430

0b98d8794a24b74ed659c1fcc64a270aa27181bb12f41b5b50e714177d46e8cf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ing-ideal-acquiring-shared (version 15.1.26).
If you installed it — respond
Remove ing-ideal-acquiring-shared 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 ing-ideal-acquiring-shared 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. ing-ideal-acquiring-shared on npm has been identified as a malicious package (version 15.1.26 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05814

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ing-ideal-acquiring-shared-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