Which versions of gibertserct15 are malicious?

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

How do I remediate gibertserct15 if I installed it?

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

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

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

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

Malicious package

gibertserct15npm

Advisory published Dec 23, 2025Updated Dec 24, 2025

gibertserct15 is a confirmed malicious npm package (MAL-2025-192799) 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 gibertserct15 (npm)

MAL-2025-192799

Immediate action

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

npm uninstall gibertserct15

What this malware does

The package gibertserct15 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

770af63ed0de01fdf5a99f9245373116f800a5622a2e41c1b7fa3032205a55bc

0dcf1ea6477d7bbd80b0e598d5b8fd059b9f00222e393308e69c08489e29e985

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gibertserct15 (version 0.30.1).
If you installed it — respond
Remove gibertserct15 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 gibertserct15 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. gibertserct15 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-06357

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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