Which versions of @mparpaillon/page are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for @mparpaillon/page (version 1.0.1).

Malicious package

@mparpaillon/pagenpm

Advisory published Nov 24, 2025Updated Dec 23, 2025

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

Malicious code in @mparpaillon/page (npm)

MAL-2025-190872

Immediate action

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

npm uninstall @mparpaillon/page

What this malware does

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

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

fbc632dc769c1c17211f5a14d8e9f40217a70b214e5a367f0ab8fccc939332a1

b27da92201393052dbce684f17cec3c9bc9d87c220a7b7658c31aa62953d2d05

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06029

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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