Which versions of gestion-usuarios are malicious?

The following npm versions of gestion-usuarios are flagged malicious: 2.0.0, 3.0.5. Treat any of these as compromised.

How do I remediate gestion-usuarios if I installed it?

Remove gestion-usuarios from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed gestion-usuarios — how do I know if it already compromised me?

If gestion-usuarios 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 gestion-usuarios part of a known attack campaign?

Yes — gestion-usuarios is associated with the GHSA-x656-6c54-m5c5, RLMA-2025-05379, RLUA-2025-05804 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 gestion-usuarios 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 gestion-usuarios (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gestion-usuarios across your stack and pipelines.

Malicious package

gestion-usuariosnpm

gestion-usuarios is a confirmed malicious npm package (MAL-2025-47926) that executes malicious code on install (malicious versions 2.0.0, 3.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gestion-usuarios (npm)

MAL-2025-47926

Immediate action

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

npm uninstall gestion-usuarios

What this malware does

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

2 flagged

2.0.03.0.5

Indicators of compromise (SHA-256)

1fe0dc407db39c0fef791ed6f17adc1803bdbbe0c7c9881c50921632d16ccf09

bd77e56e6ea1549e8b0e68b4599d44e65a26d467a7f048688c41dd51e4ad85df

6ae37da00ac336044538e78562435cdbaed6f13c322d5790c871c207e9284b31

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gestion-usuarios (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gestion-usuarios across your stack and pipelines.
If you installed it — respond
Remove gestion-usuarios from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If gestion-usuarios 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 gestion-usuarios 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. gestion-usuarios on npm has been identified as a malicious package (versions 2.0.0, 3.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x656-6c54-m5c5RLMA-2025-05379RLUA-2025-05804

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gestion-usuarios-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database