Which versions of swissid-common are malicious?

The following npm versions of swissid-common are flagged malicious: 0.0.1, 1.0.0, 99.0.0. Treat any of these as compromised.

How do I remediate swissid-common if I installed it?

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

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

Yes — swissid-common is associated with the GHSA-r5fr-fvr3-8vpc, RLMA-2025-06507, RLUA-2026-01602 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 swissid-common 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 swissid-common (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swissid-common across your stack and pipelines.

Malicious package

swissid-commonnpm

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

MAL-2025-192583

Immediate action

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

npm uninstall swissid-common

What this malware does

The package swissid-common 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

3 flagged

0.0.11.0.099.0.0

Indicators of compromise (SHA-256)

2657ec223bbf476c870a3f34e60928d95b1512176e7762f2c01a9aa759f75d98

68ce12ad99bb87750b22a3aa2c0d4bae036e647f446f6c05eb46b7fad1571d13

724e43dfb6de3b2d115d47cf07493d02453bca1421aba6b9a9d1ac0a0fd4bc15

ff7e7de14d06f6fa23b23c79f1c2ecdb2972949468cfc50c4f45982e2eef08f4

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

Campaign

GHSA-r5fr-fvr3-8vpcRLMA-2025-06507RLUA-2026-01602

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks swissid-common-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