Threat Analysis: npm Supply Chain Attack, Five Eyes China Warning, and NCSC Dependency Alert
Hello, Mauven here.
This is your Daily Threat Analysis for 4th June 2026.
Three separate items landed today with direct relevance to UK SMBs and anyone who manages IT on their behalf. Each one is significant on its own. Together, they paint a picture of the week’s threat landscape that is worth understanding before your developers push another update or your sales team accepts another LinkedIn connection request.
1. The npm Supply Chain Attack That Bypassed the Checks You Think Are Working
On 2nd June, Microsoft Threat Intelligence published detailed findings on what they are calling the Miasma campaign: a supply chain attack that compromised 32 npm packages published across more than 90 versions under the @redhat-cloud-services scope.
That scope is significant. These were not random packages from an unknown developer. They sat under a namespace associated with Red Hat, a trusted, widely used vendor, and the malicious versions carried authentic provenance signatures generated through legitimate GitHub Actions OIDC workflows. In practical terms, that means the standard checks many development teams rely on to verify package integrity would have passed them through without issue.
The mechanism of compromise was the CI/CD pipeline of the RedHatInsights/javascript-clients repository. Once attackers had access to that pipeline, they could publish trojanised packages that looked, to automated tooling, entirely legitimate.
The payload was credential theft. The packages were designed to exfiltrate sensitive data, tokens, credentials, environment variables, from any system where they were installed.
What this means for UK SMBs
If your business uses a managed service provider, a development agency, or any internal team that builds or maintains software using Node.js, there is a non-trivial chance that npm packages touched by this or similar campaigns are somewhere in your dependency tree. Most small businesses have no visibility into what their IT providers are running. Most IT providers, frankly, have limited visibility into their own transitive dependencies.
The advisory does not say how many UK organisations were affected. It would not, because that number is not knowable from the outside. What it does say is that the attack worked by exploiting the trust that the open-source ecosystem places in verified provenance, and that trust, as of this week, has been demonstrably abused.
This is not the first time a legitimate-looking package in a trusted namespace has been used as a delivery mechanism. It will not be the last.
2. The NCSC Asks, Again, That You Check Your Dependencies
Also published today: a blog post from the NCSC urging organisations to review their open-source dependencies and reduce their exposure to supply chain attacks.
The timing is not coincidental. The Miasma campaign is almost certainly part of the context.
The NCSC has published guidance on software supply chain security in various forms since at least 2019. The fact that a new post was necessary in June 2026, asking organisations to do the same things the guidance has recommended for years, tells you exactly how seriously most organisations have taken the previous versions.
To be fair to the NCSC, the guidance is sound. The blog asks defenders to maintain an accurate inventory of dependencies, understand where packages come from, monitor for unexpected changes, and assess the trustworthiness of upstream sources. All of that is correct. All of it has been correct for years.
The gap is not knowledge. The gap is implementation. A UK SMB with three people in IT and a managed service provider handling the rest does not have a mature software composition analysis process. Most do not have any process at all beyond trusting that what their provider installs is legitimate.
If you are in that position, the actionable step today is not to read the NCSC guidance in full, though you should, but to ask whoever manages your technology estate one specific question: How do you verify that the packages and dependencies you install on our systems have not been tampered with?
If the answer is vague, that is useful information.
3. Five Eyes Warns on Chinese LinkedIn Recruitment, What the Advisory Does Not Say
Also today, a Five Eyes joint advisory, with MI5 among the signatories, warned that China is actively using LinkedIn to recruit individuals with access to sensitive government and commercial information.
The tradecraft is well-documented. Fake or semi-legitimate professional profiles contact targets with research opportunities, consulting work, or conference invitations. Initial contact is benign. The relationship is cultivated over weeks or months before any request for sensitive information is made. Payment in cryptocurrency is sometimes offered.
The advisory is described as a warning about an expanding campaign. What it does not say, and what the intelligence record does say, is that this tradecraft has been observed and reported on since at least 2018. The NCSC and its Five Eyes partners have warned about it before. The campaign did not begin this week.
What the advisory is actually communicating, if you read between the lines, is that the tempo or targeting has shifted enough to warrant a new public statement. That is worth noting.
The SMB angle here is indirect but real
Most small businesses are not direct targets of Chinese state-sponsored espionage. But they employ people who hold LinkedIn profiles. Those people may have connections to clients in defence, professional services, financial services, or public sector work. They may themselves hold Cyber Essentials certifications or work adjacent to government supply chains.
TA4922, a suspected Chinese-speaking threat actor documented by Proofpoint this week, has expanded its operations from East Asia to Europe and Africa, deploying multiple malware families including Atlas RAT and ValleyRAT. This group is not going after small businesses directly. It is going after their clients, their partners, and their sector adjacencies.
The immediate practical step is straightforward: make sure your staff know that unsolicited LinkedIn contact from researchers, academics, or recruiters offering unusually attractive consulting opportunities is a known social engineering vector. Brief them. It takes ten minutes.
Also Worth Noting: Cisco Unified CM PoC Exploit
Cisco has patched a critical vulnerability in Unified Communications Manager that allows an attacker to gain root privileges. A proof-of-concept exploit is already in circulation, which shortens the window between disclosure and exploitation significantly.
If your business uses Cisco Unified CM, or if your telephony is managed by a provider who does, check with them today that the patch has been applied. A PoC in the wild means this moves from theoretical to actively exploitable within days, not weeks.
What to Do Today
- Ask your IT provider how they audit npm and open-source dependencies for tampering. If they cannot answer clearly, escalate.
- Brief any staff with LinkedIn profiles on the social engineering pattern described in the Five Eyes advisory. Particularly relevant for anyone with defence, government, or financial sector connections.
- If you use Cisco Unified CM, confirm with your provider that this week’s patch has been applied and get a date if it has not.
- Read the NCSC supply chain blog if you have any development capability in-house: ncsc.gov.uk/blogs/software-supply-chain-attacks-check-your-dependencies