VYPR
Vypr IntelligenceAI-generatedOct 16, 2026

npm: 14 Malicious Packages in '@beloved-lenora/opencode-' Campaign Disclosed Simultaneously

On October 16, 2026, 14 malicious npm packages, all part of the `@beloved-lenora/opencode-` campaign, were simultaneously disclosed, indicating a coordinated supply chain attack.

Key findings

  • 14 malicious npm packages disclosed simultaneously on October 16, 2026
  • All packages share the @beloved-lenora npm scope and @beloved-lenora/opencode- prefix
  • Packages were first published just one day before their disclosure
  • Advisories uniformly classify the packages with 'Critical' severity
  • Attack indicates a coordinated effort to inject malicious modules into npm

On October 16, 2026, 14 malicious packages were simultaneously disclosed on npm, all sharing the @beloved-lenora scope and @beloved-lenora/opencode- prefix. These packages, first published just one day prior to their disclosure, were flagged and removed from the registry at 18:49 UTC, indicating a rapid response to a newly launched campaign.

The coordinated nature of this disclosure is evident in the consistent naming convention employed by the attackers. All 14 packages fall under the @beloved-lenora npm scope and share the common prefix @beloved-lenora/opencode-. This pattern suggests an automated or highly organized effort to flood the registry with malicious modules. Examples include @beloved-lenora/opencode-btw, @beloved-lenora/opencode-shared-rpc, @beloved-lenora/opencode-stats, @beloved-lenora/opencode-goal, and @beloved-lenora/opencode-orchestrator.

While specific behavioral findings from OpenSSF Package Analysis were not detailed in the advisories, the consistent 'Critical' severity assigned to many of these packages strongly implies severe malicious intent. Typically, such packages aim to compromise developer environments, exfiltrate sensitive data, or establish persistent backdoors.

The advisories uniformly classify these packages with 'Critical' severity. This designation means that any system that installed these malicious modules should be considered fully compromised. Developers are strongly advised to treat affected machines as untrusted, rotate all credentials and secrets from a separate, secure machine, and thoroughly audit their development environments for any unauthorized changes or persistent threats.

Developers should immediately audit their package-lock.json files and dependency trees for any packages matching the @beloved-lenora/opencode- naming convention. If any of these packages are found, they must be removed, and a comprehensive incident response plan should be initiated. This includes rotating all npm tokens, SSH keys, and other sensitive credentials that may have been exposed, as well as checking npm token logs for any unauthorized publish activity. A representative list of affected packages includes:

  • @beloved-lenora/opencode-btw
  • @beloved-lenora/opencode-shared-rpc
  • @beloved-lenora/opencode-stats
  • @beloved-lenora/opencode-goal
  • @beloved-lenora/opencode-todo
  • @beloved-lenora/opencode-orchestrator
  • @beloved-lenora/opencode-shell-guard

This incident highlights the ongoing threat of supply chain attacks targeting package ecosystems like npm. The rapid disclosure of these packages, published just hours before their removal, underscores the vigilance required by security teams and the importance of automated detection systems in identifying and mitigating such threats swiftly. The use of a consistent naming scheme suggests a deliberate, albeit unsophisticated, attempt to inject malicious code into the developer supply chain.

AI-written article. Grounded in 0 CVE records listed below.