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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mparpaillon/connector-parse (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mparpaillon/connector-parse across your stack and pipelines.

Malicious package

@mparpaillon/connector-parsenpm

Malicious code in @mparpaillon/connector-parse (npm) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mparpaillon/connector-parse (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mparpaillon/connector-parse across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @mparpaillon/connector-parse before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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