Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @pagseguro published 15 malicious packages. See the full campaign →
Malicious package

@pagseguro/pagseguro-utilsnpm

Advisory published Updated

@pagseguro/pagseguro-utils is a confirmed malicious npm package (MAL-2023-47) that steals credentials and exfiltrates sensitive data (malicious versions 3.10.1, 10.0.0, 10.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @pagseguro/pagseguro-utils (npm)

MAL-2023-47
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @pagseguro/pagseguro-utils

What this malware does

Malicious packages campaign since 2021 targeting developers, steals source code and secrets

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 '@pagseguro/pagseguro-utils' @ 10.0.1 (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

3 flagged
3.10.110.0.010.0.1

Indicators of compromise (SHA-256)

81544815ad1130df749e3129c5142b499e8c20cd6f9737255a53307194635c7f
86753457991d0a20bcc1af0b088217f314fac419c62d6391a59275fe46c2170f
a7b37fd8fd01c941997166b66a6220a2b578e11958ce74699f29c85bbdeadcec
cdd1223d2de78ddd3cbb0cd5926ae9a52a0d2127aa5ee468cfecbf526b9173c8
8e3f853a167ac4fc6f37a0c3b1b12bdba5e57f568800476f319399643b6b0fa9

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @pagseguro/pagseguro-utils (3 malicious versions).

  2. If you installed it — respond

    @pagseguro/pagseguro-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @pagseguro/pagseguro-utils 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. @pagseguro/pagseguro-utils on npm has been identified as a malicious package (versions 3.10.1, 10.0.0, 10.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3pm8-p93m-8j38

References

Credits

  • Checkmarx · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @pagseguro/pagseguro-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@pagseguro/pagseguro-utils (npm) malicious package — MAL-2023-47 | O3 Security