Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in @forjacms/client (npm)

0
High
Published: 06/05/2026 (06/05/2026, 00:53:43 UTC)
Source: GCVE Database
Product: @forjacms/client

Description

The npm package @forjacms/client versions 1.8.4 and 1.8.5 contain malicious code associated with the Miasma malware. This malware propagates by abusing weaponized binding.gyp files to execute code during package installation, bypassing security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and spreads by compromising other packages or committing backdoors to GitHub repositories.

Affected software

npmghsa
@forjacms/client
Affected versions
=1.8.4=1.8.5

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/09/2026, 10:09:11 UTC

Technical Analysis

The @forjacms/client npm package versions 1.8.4 and 1.8.5 were found to contain malicious code linked to the Miasma malware. Miasma is a self-propagating worm that leverages weaponized binding.gyp files to execute during package installation, circumventing detection by security tools focused on lifecycle scripts. Upon execution, it attempts to steal credentials and OIDC tokens for various cloud and registry services. The malware then propagates by compromising other npm packages managed by the stolen accounts or by injecting backdoor files into GitHub repositories, facilitating further spread and persistence.

Potential Impact

Malicious code in the affected package versions can lead to credential and token theft for cloud and registry services, enabling unauthorized access. This can result in further compromise of other npm packages and GitHub repositories through propagation mechanisms. Although no known exploits in the wild are reported, the potential for widespread compromise exists due to the malware's self-propagating nature.

Mitigation Recommendations

No official patch or remediation is currently documented for the affected versions. Users should avoid using @forjacms/client versions 1.8.4 and 1.8.5. Monitor vendor advisories for updates or fixes. Consider removing or replacing the affected package versions in your environment to prevent potential compromise.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-5206
Osv Schema Version
1.7.4
Aliases
[]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a4f6c7768715ace4315ad47

Added to database: 07/09/2026, 09:40:07 UTC

Last enriched: 07/09/2026, 10:09:11 UTC

Last updated: 07/28/2026, 19:05:56 UTC

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses