Which versions of apple-internal-telemetry-service are malicious?

The following npm versions of apple-internal-telemetry-service are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate apple-internal-telemetry-service if I installed it?

apple-internal-telemetry-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed apple-internal-telemetry-service — how do I know if it already compromised me?

If apple-internal-telemetry-service 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 apple-internal-telemetry-service part of a known attack campaign?

Yes — apple-internal-telemetry-service is associated with the GHSA-g2w3-7m75-fpwv 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 apple-internal-telemetry-service 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 apple-internal-telemetry-service (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apple-internal-telemetry-service across your stack and pipelines.

Malicious package

apple-internal-telemetry-servicenpm

Malicious code in apple-internal-telemetry-service (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3161

Immediate action

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

npm uninstall apple-internal-telemetry-service

What this malware does

Malicious npm package published by threat actor "raya4321" as part of a coordinated typosquatting campaign impersonating Apple internal infrastructure services (authentication, PKI, telemetry, CloudKit, and cloud infrastructure). All packages in this campaign execute credential-theft payloads during npm installation via preinstall or postinstall lifecycle hooks.

Trigger: postinstall. Conditionally triggers on Apple-named hosts or environments; exfiltrates system info (hostname, uname), environment variables, and SSH private keys to https://franki.requestcatcher.com/apple_verified_leak via curl.

The package apple-internal-telemetry-service 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

1.0.0

Indicators of compromise (SHA-256)

fe7741fa4f530a8a59ac376392387c8ac6f92e57fbf0c521d17d9a84a3c1a6a8

7ed7c60e615cd67997c18026842f63aea7088c1eb36a8deaf489c1ba98917db8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for apple-internal-telemetry-service (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apple-internal-telemetry-service across your stack and pipelines.
If you installed it — respond
apple-internal-telemetry-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If apple-internal-telemetry-service 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 apple-internal-telemetry-service 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. apple-internal-telemetry-service on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g2w3-7m75-fpwv

References

github.com

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks apple-internal-telemetry-service-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring