MAL-2026-4382 Malicious code in @djessicatony/folk-mcp-canary (npm)
Malicious package
Published
MAL-2026-4382 is a malicious package: @djessicatony/folk-mcp-canary (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4382/ (Markdown: https://insights.sbomify.com/MAL-2026-4382/index.md)
- Package
- @djessicatony/folk-mcp-canary
- Registry
- npm
What is MAL-2026-4382?
MAL-2026-4382 is a malicious package in @djessicatony/folk-mcp-canary, published on 21 May 2026.
Official description
index.js contains a beacon-style exfiltration primitive: a fetch() POST at line 60-61 sends process.env data (read at lines 30 and 34) to a hardcoded destination URL (https://REPLACE-WITH-YOUR-BEACON.example, observed at line 24). The file also references 'ping' command invocations (lines 3, 83, 92) consistent with host reconnaissance. The destination URL is a placeholder template string ('REPLACE-WITH-YOUR-BEACON.example'), indicating this is either a published-by-mistake attack template or a proof-of-concept beacon stub — either way the structural shape (env-var read + POST to hardcoded non-publisher endpoint) is an installer-data exfiltration pattern with no legitimate purpose. Package name (under @djessicatony scope, suffix 'canary', version 0.0.1) and the placeholder C2 are consistent with throwaway test-publish of malicious tooling.
What should I do about MAL-2026-4382?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.