Which versions of serval-integrations-common-frontend are malicious?

The following npm versions of serval-integrations-common-frontend are flagged malicious: 7.0.0. Treat any of these as compromised.

How do I remediate serval-integrations-common-frontend if I installed it?

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

If serval-integrations-common-frontend 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 serval-integrations-common-frontend part of a known attack campaign?

Yes — serval-integrations-common-frontend is associated with the GHSA-3j9j-c9rg-f95f, RLMA-2025-06477, RLUA-2026-01557 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 serval-integrations-common-frontend 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 serval-integrations-common-frontend (version 7.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging serval-integrations-common-frontend across your stack and pipelines.

Malicious package

serval-integrations-common-frontendnpm

Malicious code in serval-integrations-common-frontend (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192401

Immediate action

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

npm uninstall serval-integrations-common-frontend

What this malware does

The package serval-integrations-common-frontend was found to contain malicious code.

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

7.0.0

Indicators of compromise (SHA-256)

4851f2ee0cbb1d68f7476139256684559c35db2559afff037bdef4fc4cda216e

034a79cdc705d00ab7fb639f1d90c46135f42d8f6cf57eef63bf822adbffac48

28ed9c1bedc0b9e85aa5367eaaac857d20748476934bcbe55c7bcc6457d85132

ef7416755a5bf58f6f99f93bba4120969645968887f64d667293fd97f9852bf0

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

Campaign

GHSA-3j9j-c9rg-f95fRLMA-2025-06477RLUA-2026-01557

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks serval-integrations-common-frontend-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