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-utils-testnpm

@pagseguro/pagseguro-utils-test is a confirmed malicious npm package (MAL-2023-1098) that steals credentials and exfiltrates sensitive data (malicious version 1.999.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

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

The OpenSSF Package Analysis project identified '@pagseguro/pagseguro-utils-test' @ 1.999.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

1 flagged
1.999.1

Indicators of compromise (SHA-256)

c80d50a5d149e186763199f475ecd3c23a25e41c93cabeea13494c6bf8c1641a
1ca218112e7cf19df5928168bb7ac862f943cd50af825db0fd09289b710a719d

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

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

References

Credits

  • Checkmarx · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@pagseguro/pagseguro-utils-test (npm) malicious package — MAL-2023-1098 | O3 Security