Which versions of gibertserct8 are malicious?

The following npm versions of gibertserct8 are flagged malicious: 0.30.1. Treat any of these as compromised.

How do I remediate gibertserct8 if I installed it?

Remove gibertserct8 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 gibertserct8 — how do I know if it already compromised me?

If gibertserct8 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.

Is gibertserct8 part of a known attack campaign?

Yes — gibertserct8 is associated with the RLMA-2025-06358 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 gibertserct8 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gibertserct8 (version 0.30.1).

Malicious package

gibertserct8npm

Advisory published Dec 23, 2025Updated Dec 24, 2025

gibertserct8 is a confirmed malicious npm package (MAL-2025-192800) that executes malicious code on install (malicious version 0.30.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gibertserct8 (npm)

MAL-2025-192800

Immediate action

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

npm uninstall gibertserct8

What this malware does

The package gibertserct8 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

90e38c2ae8f4559fca5b58a78559354f9cbc5f710b75e4c1fee5909b22d91f48

0583648056f2d0e73c6a06de3a44a2febda71c4cab85423fe2d051435206f0f5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gibertserct8 (version 0.30.1).
If you installed it — respond
Remove gibertserct8 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 gibertserct8 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. gibertserct8 on npm has been identified as a malicious package (version 0.30.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06358

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gibertserct8-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