Which versions of @marketplace-shared/components are malicious?

The following npm versions of @marketplace-shared/components are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @marketplace-shared/components if I installed it?

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

If @marketplace-shared/components 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 @marketplace-shared/components part of a known attack campaign?

Yes — @marketplace-shared/components is associated with the GHSA-5cx4-3w47-xm4h, RLMA-2026-04755, RLUA-2026-05437 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 @marketplace-shared/components 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 @marketplace-shared/components (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @marketplace-shared/components across your stack and pipelines.

Malicious package

@marketplace-shared/componentsnpm

@marketplace-shared/components is a confirmed malicious npm package (MAL-2026-5658) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @marketplace-shared/components (npm)

MAL-2026-5658

Immediate action

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

npm uninstall @marketplace-shared/components

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

98933a5f467c2a623815ed46e5baf6838ba6e86e8055b48d4941da3bf59e5c41

ae29e2c7399ae835dc71267d14750ce0b8e85e99631c4370957189306564f7b0

8b7a6069fce8de6cc0649bf328cc9bd14c2d41c824fcd7d09e30045072897b33

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 @marketplace-shared/components (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @marketplace-shared/components across your stack and pipelines.
If you installed it — respond
Remove @marketplace-shared/components 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 @marketplace-shared/components 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 @marketplace-shared/components 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. @marketplace-shared/components on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5cx4-3w47-xm4hRLMA-2026-04755RLUA-2026-05437

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @marketplace-shared/components-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