Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

revolut-merchant-widgetnpm

Malicious code in revolut-merchant-widget (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1481
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall revolut-merchant-widget

What this malware does

The package revolut-merchant-widget 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.

The OpenSSF Package Analysis project identified 'revolut-merchant-widget' @ 999.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
999.0.1

Indicators of compromise (SHA-256)

6919e4d5f489ccb2afdb09b3fcbff6c0ea8c21dde36675e8188d5c0ba3ec5b67
be3c58d0da88dbc307fda899df07f7e6badfcba4ccb5f98ce68e1daef3caa8c7
575d62e38713631575155bf621102ddf8a4c2324bdc63a87800c1ef78ac3596f

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove revolut-merchant-widget 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.

  3. Did it already run?

    If revolut-merchant-widget 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.

  4. How O3 protects you

    O3 blocks revolut-merchant-widget 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. revolut-merchant-widget on npm has been identified as a malicious package (version 999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gpc2-rm7h-fpc4

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks revolut-merchant-widget-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.

revolut-merchant-widget (npm) malicious package — MAL-2026-1481 | O3 Security