Malicious code in @amber-team/gatsby-plugin-semcore (npm)
The npm package @amber-team/gatsby-plugin-semcore was found to contain malicious code. The package was identified by the OpenSSF malicious packages project and reported via GitHub Security Advisory GHSA-27jr-546m-cv6p.
- Disclosed
- Last updated
- Blast radius
- Unknown; depends on adoption of affected versions
- Ecosystems
- Attack vectors
- Affected entities
- @amber-team/gatsby-plugin-semcore
The npm package @amber-team/gatsby-plugin-semcore was identified as containing malicious code. The discovery was credited to the OpenSSF's malicious packages project, which maintains a repository of known malicious software supply chain incidents.\n\nThe advisory was published on 2026-07-26 and assigned GitHub Security Advisory identifier GHSA-27jr-546m-cv6p. The malicious package entry is tracked in the OpenSSF malicious packages repository under identifier MAL-2025-7058.\n\nNo specific details regarding the nature of the malicious code, affected versions, or remediation steps beyond package removal are provided in the source material.
Indicators of compromise
- Packages
- @amber-team/gatsby-plugin-semcore
Remediation
- Remove @amber-team/gatsby-plugin-semcore from all projects and dependencies
- Audit project dependencies for any other packages from the same author or organization
- Review project history for any suspicious activity or data exfiltration that may have occurred while the malicious package was installed
- Update to a safe alternative package if the functionality is required
Sources
- GitHub Advisory GHSA-27jr-546m-cv6p · GitHub Advisory Database
Cite this entry
"Malicious code in @amber-team/gatsby-plugin-semcore (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-amber-team-gatsby-plugin-semcore-npm-7av8zv
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package