Which versions of @mparpaillon/imagesloaded are malicious?

The following npm versions of @mparpaillon/imagesloaded are flagged malicious: 4.1.2. Treat any of these as compromised.

How do I remediate @mparpaillon/imagesloaded if I installed it?

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

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

Yes — @mparpaillon/imagesloaded is associated with the RLMA-2025-06028 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 @mparpaillon/imagesloaded across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mparpaillon/imagesloaded (version 4.1.2).

Malicious package

@mparpaillon/imagesloadednpm

Advisory published Nov 24, 2025Updated Dec 23, 2025

@mparpaillon/imagesloaded is a confirmed malicious npm package (MAL-2025-190871) that executes malicious code on install (malicious version 4.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mparpaillon/imagesloaded (npm)

MAL-2025-190871

Immediate action

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

npm uninstall @mparpaillon/imagesloaded

What this malware does

The package @mparpaillon/imagesloaded was found to contain malicious code.

Malicious versions

1 flagged

4.1.2

Indicators of compromise (SHA-256)

733f9cddc9163f876de6db1b1dab8c6325aa55f34f478662321875c52f242ea4

506e977605745b6dcf2edcfac3bf4e93db53a7e8b954f02ea12ea95cdffbef6d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06028

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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