Which versions of @pagseguro/ps-crypt-js are malicious?

Every published version of @pagseguro/ps-crypt-js on npm is considered malicious. Remove the package entirely.

How do I remediate @pagseguro/ps-crypt-js if I installed it?

@pagseguro/ps-crypt-js 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/ps-crypt-js — how do I know if it already compromised me?

If @pagseguro/ps-crypt-js 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.

How do I find @pagseguro/ps-crypt-js across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@pagseguro/ps-crypt-jsnpm

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

Malicious code in @pagseguro/ps-crypt-js (npm)

MAL-2023-7999

Immediate action

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

npm uninstall @pagseguro/ps-crypt-js

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)

40a6f6bf343548e89c4d7feaa6420d2c19f90bf043babf42602824d186d4a691

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @pagseguro/ps-crypt-js (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @pagseguro/ps-crypt-js across your stack and pipelines.
If you installed it — respond
@pagseguro/ps-crypt-js 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/ps-crypt-js 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.
How O3 protects you
O3 blocks @pagseguro/ps-crypt-js 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/ps-crypt-js 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/ps-crypt-js-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