Which versions of @mparpaillon/connector-parse are malicious?

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

How do I remediate @mparpaillon/connector-parse if I installed it?

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

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

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

Search your lockfiles and build artifacts for @mparpaillon/connector-parse (version 1.0.1).

Malicious package

@mparpaillon/connector-parsenpm

Advisory published Nov 24, 2025Updated Dec 23, 2025

@mparpaillon/connector-parse is a confirmed malicious npm package (MAL-2025-190870) 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/connector-parse (npm)

MAL-2025-190870

Immediate action

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

npm uninstall @mparpaillon/connector-parse

What this malware does

The package @mparpaillon/connector-parse was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

ffec89e4bd3b2d309b636261098474ed4816b5b9bd40872855c24c082de3666c

fd0b144ccf46c26b573ad6529c660984a3c361d857bd2f3c0866845d1304443f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mparpaillon/connector-parse (version 1.0.1).
If you installed it — respond
Remove @mparpaillon/connector-parse 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/connector-parse 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/connector-parse 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-06027

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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