NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@paysafe-tracking/error-monitoringnpm

Advisory published Updated

@paysafe-tracking/error-monitoring is a confirmed malicious npm package (MAL-2026-3360) that executes malicious code on install (malicious versions 8.0.1, 8.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @paysafe-tracking/error-monitoring (npm)

MAL-2026-3360
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @paysafe-tracking/error-monitoring

What this malware does

The package @paysafe-tracking/error-monitoring was found to contain malicious code.

The OpenSSF Package Analysis project identified '@paysafe-tracking/error-monitoring' @ 8.0.3 (npm) as malicious.

It is considered malicious because:

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

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
8.0.18.0.3

Indicators of compromise (SHA-256)

8010d5af19535a1de804f3b269e14bc9eaabdcfb9a254d6f1cbcba6ac43286a5
9320fd5f40665fca83dc28081829409ecc5593d321cc0af003092a4f70f65eb9
9c2acf9c4e0793663b7ca39f1c5c5a4646e8cecb488863494d904cdce97e01df

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @paysafe-tracking/error-monitoring (2 malicious versions).

  2. If you installed it — respond

    Remove @paysafe-tracking/error-monitoring 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 @paysafe-tracking/error-monitoring 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. @paysafe-tracking/error-monitoring on npm has been identified as a malicious package (versions 8.0.1, 8.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

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

Detect & block this

O3 blocks @paysafe-tracking/error-monitoring-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.

Explore

@paysafe-tracking/error-monitoring (npm) malicious package — MAL-2026-3360 | O3 Security