npm: 10 Malicious Packages Impersonate Internal Apple and Google Cloud Tools in Instant Drop

Key findings

• Ten malicious npm packages disclosed simultaneously on September 3, 2026.
• Packages impersonated internal development tools for Apple and Google Cloud.
• All packages were newly published, just hours before their disclosure.
• The campaign included packages with the frank- prefix and company-specific internal-sounding names.
• All advisories were rated with Critical severity, indicating severe potential compromise.

On September 3, 2026, ten malicious packages were simultaneously disclosed on the npm registry, all within the same minute. These packages, which were all published just eight hours prior to their disclosure, appear to be part of a coordinated campaign designed to impersonate internal development tools and services associated with major technology companies like Apple and Google Cloud. The rapid publication and subsequent takedown indicate a swift response to a targeted supply chain attack.

The campaign exhibits a clear pattern of naming conventions aimed at deceiving developers into believing they are installing legitimate internal utilities. Several packages utilize the frank- prefix, such as frank-apple-utils, frank-apple-sync-service, and frank-research-poc-apple, suggesting a common origin or actor. Other packages directly mimic internal tools for specific companies, including apple-cktool-internal-api-v9 and apple-internal-test-utility for Apple, and google-cloud-internal-core-utils, google-internal-cloud-audit-security-check, google-cloud-internal-build-helper, and google-cloud-mono-repo-helper for Google Cloud. The inclusion of terms like "internal," "cloud," "api," "sync-service," and "helper" in these names is a deliberate tactic to suggest authenticity and utility within a corporate development environment.

While specific behavioral findings from OpenSSF Package Analysis were not detailed in the advisories, all ten packages were assigned a Critical severity rating. This classification typically indicates that the malicious code, if executed, could lead to severe consequences such as remote code execution, credential exfiltration, or complete system compromise. Malicious packages designed to impersonate internal tools often aim to steal sensitive information like API keys, environment variables, or source code, or to establish backdoors for persistent access to developer machines or build environments.

The Critical severity assigned to these packages means that any system that installed one or more of these malicious components should be considered fully compromised. The potential impact is profound, as an attacker could gain unauthorized access to sensitive data, inject further malicious code, or move laterally within a compromised network. Users are strongly advised to treat any affected system as untrusted and to take immediate remediation steps.

Developers should immediately audit their project dependencies by checking their package-lock.json or yarn.lock files for the presence of any of the following package names: frank-apple-utils frank-apple-sync-service apple-cktool-internal-api-v9 frank-research-poc-apple google-cloud-internal-core-utils frank-bot-gogle-cloning google-internal-cloud-audit-security-check apple-internal-test-utility google-cloud-internal-build-helper google-cloud-mono-repo-helper If any of these packages are found, they must be removed immediately. Furthermore, all credentials, API keys, and sensitive tokens used in the affected development environment or associated with the compromised project should be rotated from a separate, secure machine. It is also crucial to investigate for any unauthorized activity or data exfiltration that may have occurred.

This incident highlights the ongoing threat of software supply chain attacks, where attackers leverage deceptive package names to infiltrate development ecosystems. The strategy of impersonating internal tools is particularly insidious, as it preys on developers' trust in familiar naming conventions and the need for specialized utilities. The rapid disclosure and removal of these packages demonstrate the importance of continuous monitoring and swift action by registry maintainers and security researchers in mitigating such threats. However, the onus remains on developers to maintain vigilance and scrutinize their dependencies, even those that appear to be benign or internally sourced.