Which versions of getd-pantallas-cliente are malicious?

The following npm versions of getd-pantallas-cliente are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate getd-pantallas-cliente if I installed it?

getd-pantallas-cliente 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 getd-pantallas-cliente — how do I know if it already compromised me?

If getd-pantallas-cliente 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.

Is getd-pantallas-cliente part of a known attack campaign?

Yes — getd-pantallas-cliente is associated with the IN-MAL-2026-005213, IN-MAL-2026-005214, GHSA-jgp5-45jr-pqpc, RLMA-2026-05543 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find getd-pantallas-cliente 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 getd-pantallas-cliente (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getd-pantallas-cliente across your stack and pipelines.

Malicious package

getd-pantallas-clientenpm

Malicious code in getd-pantallas-cliente (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5468

Immediate action

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

npm uninstall getd-pantallas-cliente

What this malware does

On npm install, postinstall.js collects os.hostname(), os.userInfo().username, os.platform(), process.cwd(), and CI/build environment variables and sends them as URL query parameters via HTTPS GET to an anonymous webhook.site endpoint (https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5). Errors are silently swallowed; there is no opt-in or disclosure. The package's own package.json description self-identifies as a typosquat placeholder for the @getd/* scope, so any installer who mistypes a scoped package name has their machine fingerprinted and shipped to a third-party endpoint outside their control. Regardless of the author's stated 'defensive research' framing, the on-install behavior is unconsented exfiltration of installer-identifying data to an anonymous, ephemeral destination.

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

89a26267435645776aa984be114d5c657e63fa9937ff044e5ddd24943b28ea6e

a4e55187e25f0b708b05c376db9bfd9ceeebdd32131d5dd15ade11a8811dcbdc

8b712c7b54fc03c2e57cd7178e1410a6f9dcabebdc63b73a9e00fc96a0e81d68

85a7a5aa53baf8d0afbd524d7404f456e146b5fae50037312ed957c89e39d755

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 getd-pantallas-cliente (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getd-pantallas-cliente across your stack and pipelines.
If you installed it — respond
getd-pantallas-cliente 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 getd-pantallas-cliente 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 getd-pantallas-cliente 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. getd-pantallas-cliente on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005213IN-MAL-2026-005214GHSA-jgp5-45jr-pqpcRLMA-2026-05543

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks getd-pantallas-cliente-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