Which versions of @afg-ikea/ikea-family-registration-module are malicious?

The following npm versions of @afg-ikea/ikea-family-registration-module are flagged malicious: 0.0.1-security, 99.9.9. Treat any of these as compromised.

How do I remediate @afg-ikea/ikea-family-registration-module if I installed it?

Remove @afg-ikea/ikea-family-registration-module 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 @afg-ikea/ikea-family-registration-module — how do I know if it already compromised me?

If @afg-ikea/ikea-family-registration-module 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 @afg-ikea/ikea-family-registration-module part of a known attack campaign?

Yes — @afg-ikea/ikea-family-registration-module is associated with the GHSA-wx5g-qvrw-cmg9, RLMA-2026-00963 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 @afg-ikea/ikea-family-registration-module 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 @afg-ikea/ikea-family-registration-module (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @afg-ikea/ikea-family-registration-module across your stack and pipelines.

Malicious package

@afg-ikea/ikea-family-registration-modulenpm

Malicious code in @afg-ikea/ikea-family-registration-module (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-517

Immediate action

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

npm uninstall @afg-ikea/ikea-family-registration-module

What this malware does

The package @afg-ikea/ikea-family-registration-module 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

2 flagged

0.0.1-security99.9.9

Indicators of compromise (SHA-256)

c1f5feb8399474167c6ea9602baa06fff5a507dfbe31f7fcab8a319bc214cce9

d1ac39afe31e807b61c9297e45f81042917f9e889e1ceb953fcaeba093c75576

f52810f68f53480c5a28b0a5e60616ad5e326a5c16465cad4d32cfeb73fbb713

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

Campaign

GHSA-wx5g-qvrw-cmg9RLMA-2026-00963

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @afg-ikea/ikea-family-registration-module-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