Which versions of @pagseguro/nest are malicious?

Every published version of @pagseguro/nest on npm is considered malicious. Remove the package entirely.

How do I remediate @pagseguro/nest if I installed it?

@pagseguro/nest 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.

I already installed @pagseguro/nest — how do I know if it already compromised me?

If @pagseguro/nest 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.

How do I find @pagseguro/nest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @pagseguro/nest (all published versions).

Part of a larger attack: @pagseguro published 15 malicious packages. See the full campaign →

Malicious package

@pagseguro/nestnpm

Advisory published Feb 23, 2023Updated Sep 1, 2023

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

Malicious code in @pagseguro/nest (npm)

MAL-2023-7996

Immediate action

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

npm uninstall @pagseguro/nest

What this malware does

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

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b16a70a89161283b99538bb25fdbaecc235a75a73c7a471c98ad831fc08a7cdf

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @pagseguro/nest (all published versions).
If you installed it — respond
@pagseguro/nest 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.
Did it already run?
If @pagseguro/nest 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/nest on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

medium.com

Credits

Checkmarx · finder

Detect & block this

O3 blocks @pagseguro/nest-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