Which versions of @ikarem/telemetry are malicious?

The following npm versions of @ikarem/telemetry are flagged malicious: 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.1.3, 100.1.5, 100.1.6, 100.1.7, 100.1.8, 100.1.9, 100.1.10. Treat any of these as compromised.

How do I remediate @ikarem/telemetry if I installed it?

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

If @ikarem/telemetry 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 @ikarem/telemetry part of a known attack campaign?

Yes — @ikarem/telemetry is associated with the GHSA-5q62-g32j-g4hp 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 @ikarem/telemetry 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 @ikarem/telemetry (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikarem/telemetry across your stack and pipelines.

Malicious package

@ikarem/telemetrynpm

Malicious code in @ikarem/telemetry (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192569

Immediate action

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

npm uninstall @ikarem/telemetry

What this malware does

The package @ikarem/telemetry 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.

The OpenSSF Package Analysis project identified '@ikarem/telemetry' @ 100.0.7 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

12 flagged

100.0.4100.0.5100.0.6100.0.7100.0.8100.1.3100.1.5100.1.6100.1.7100.1.8100.1.9100.1.10

Indicators of compromise (SHA-256)

0bdd063a8851ad4a8d904b65f27870c76cf91802b339efa7b461e0dc3bd02d6b

74f76e276cfff1c10c6f88d8376485d2af6bcdcd90d66b8b9d7ee54fef906464

c075254afb72ad184bde1e7ab4771f0a4cf155bc91152a139c74520caedf98e3

f77b546bc36b17b63f295cf3ec2f0513768dbbf241dbe3cfcb51beb76dcebf83

43ab3fc889bb1c1c02a84ffa154e9db0f8f0c9cbcb591ccf01d1f9adb84ff92f

e43d2a07b55a1387aa741edace01850ec9f79a58baac8ee1897610e2b8e77cb8

482cec2384e1daf6e4b333a7883d105f0a7963c63b515787959c36f0a1065b4a

b85c591e39995b1aa19a8ce3e5e422f8f9283c3482e440cc17a1661f068c4627

bf7f22939f982be32da8ad3a49781927ccb1e7f75925423c1e5549bff53e0c35

e20be45de353e52a254a367f56a38b162aa06086fb180b7b2aa906cdce802334

fec2a22877dad892a8d24f1a75f98e9b40a44c071e65167f9a3e4cf1f2f5ea56

31185ac978eb9d45e09fafcdde66f51fa6560865697ec29650aefb8e80927837

7513e8a63dc911f75f6f529e28565959736cd8b756ec608b47e63b101622f971

b3ab8a7fd65445f7efaa96a6fdb31b19f94672546ce1c27cd742f6d218bfadde

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 @ikarem/telemetry (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikarem/telemetry across your stack and pipelines.
If you installed it — respond
Remove @ikarem/telemetry 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 @ikarem/telemetry 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 @ikarem/telemetry 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. @ikarem/telemetry on npm has been identified as a malicious package (versions 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.1.3, 100.1.5, 100.1.6, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5q62-g32j-g4hp

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @ikarem/telemetry-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