Which versions of shopify-monorail are malicious?

The following npm versions of shopify-monorail are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate shopify-monorail if I installed it?

Remove shopify-monorail 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 shopify-monorail — how do I know if it already compromised me?

If shopify-monorail 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 shopify-monorail part of a known attack campaign?

Yes — shopify-monorail is associated with the GHSA-7887-g92r-gq3x, RLMA-2025-06482, RLUA-2026-01567 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 shopify-monorail 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 shopify-monorail (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shopify-monorail across your stack and pipelines.

Malicious package

shopify-monorailnpm

Malicious code in shopify-monorail (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192566

Immediate action

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

npm uninstall shopify-monorail

What this malware does

The package shopify-monorail was found to contain malicious code.

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

1.0.0

Indicators of compromise (SHA-256)

fedb52b0658528a4cece77bf4ef96fff3b11449dbd45c44084d4308b1e4e3fae

aef2f1cf1e314cd9c5336d39ab49f2906fba52d48adadeed13adb5cf4104aa6d

0ddebfd5f0b42fadac79b160a1d41dbe85f0a5c4a149be5f3d4f3a4598c7f4c3

1bb94cf720fdc23ed7d16c4d6251910001bc8879cbe11c48143f0b824b2a9b98

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

Campaign

GHSA-7887-g92r-gq3xRLMA-2025-06482RLUA-2026-01567

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks shopify-monorail-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