Which versions of simplisafe-gatsby are malicious?

The following npm versions of simplisafe-gatsby are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate simplisafe-gatsby if I installed it?

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

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

Yes — simplisafe-gatsby is associated with the IN-MAL-2026-007432, GHSA-grcq-xfr7-4vpm, IN-MAL-2026-019798, RLMA-2026-10786 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 simplisafe-gatsby 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 simplisafe-gatsby (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging simplisafe-gatsby across your stack and pipelines.

Malicious package

simplisafe-gatsbynpm

simplisafe-gatsby is a confirmed malicious npm package (MAL-2026-6379) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simplisafe-gatsby (npm)

MAL-2026-6379

Immediate action

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

npm uninstall simplisafe-gatsby

What this malware does

On npm install, the package's preinstall hook (package.json declares "preinstall": "node index.js") executes index.js, which collects the installer's hostname, username, home directory, DNS configuration, package metadata, and the contents of /etc/passwd and /etc/hosts (via fs.readFileSync), then POSTs the collected data over HTTPS to a Burp Collaborator subdomain at xpqamgvad3ok4bc11xar5t7q8he820qp.oastify.com. The package has no advertised functionality (empty author, empty description, single recon payload file) and its name is consistent with a dependency-confusion attempt against SimpliSafe's internal Gatsby package namespace. Any machine that runs npm install against this name will leak system identity and local-account information to the attacker.

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

1.0.11.0.2

Indicators of compromise (SHA-256)

564baff2e47527f159c52c527e1ea2b93d73625f94737f4397cff99311871a18

28fdfe170233a2cc83320ece5c3ee4b6480017f27a0d1b2fb00e1048903a023b

81e6729589f310a9aacb4a16c2892f0a928f7f9bf10be00d74ee9bdb68a68785

55d6619381c88669ea6d9d4ac6f82ebfe81418a299c77fcc3a12a541f5c3e567

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

Campaign

IN-MAL-2026-007432GHSA-grcq-xfr7-4vpmIN-MAL-2026-019798RLMA-2026-10786

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks simplisafe-gatsby-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

Explore

All malware advisories How O3 detects malware Vulnerability database