Malicious code in @apicity/meta (npm)
The npm package @apicity/meta contains malicious code that references an anonymous mutable file-hosting service, litter.catbox.moe. This service is used as a second-stage payload host in a known npm supply-chain compromise campaign. The package's installer-side code fetches and executes attacker-controlled content from this unverified host, exposing consumers to potentially malicious payloads. Multiple versions of the package 0.8.0 through 0.8.6 are affected. No official patch or remediation guidance is currently available.
AI Analysis
Technical Summary
The @apicity/meta npm package versions 0.8.0 through 0.8.6 include code that references litter.catbox.moe, an anonymous and mutable file-hosting service. This host is known to be used in the TanStack/Shai-Hulud npm supply-chain compromise campaign as a second-stage payload delivery mechanism. The presence of such a host in runtime code is anomalous and indicative of malicious intent, as it allows the package to fetch and execute attacker-controlled code dynamically during installation or runtime. This behavior exposes users of the package to arbitrary code execution risks tied to the content served by the external host at the time of resolution.
Potential Impact
Consumers who install or load affected versions of @apicity/meta are exposed to arbitrary code execution risks because the package fetches and runs code from an untrusted, anonymous external host. This can lead to compromise of the user's environment, data theft, or further malware deployment. The threat is tied to the dynamic retrieval of attacker-controlled payloads, making the impact potentially severe depending on the payload served.
Mitigation Recommendations
No official patch or remediation guidance is currently available. Users should avoid installing or using affected versions of @apicity/meta (0.8.0 through 0.8.6). Consider removing the package from projects and replacing it with trusted alternatives. Monitor vendor advisories or the package repository for updates or official fixes. Due to the nature of the malicious code, manual code inspection and blocking network access to the referenced host may provide temporary mitigation.
Malicious code in @apicity/meta (npm)
Description
The npm package @apicity/meta contains malicious code that references an anonymous mutable file-hosting service, litter.catbox.moe. This service is used as a second-stage payload host in a known npm supply-chain compromise campaign. The package's installer-side code fetches and executes attacker-controlled content from this unverified host, exposing consumers to potentially malicious payloads. Multiple versions of the package 0.8.0 through 0.8.6 are affected. No official patch or remediation guidance is currently available.
Affected software
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
Technical Analysis
The @apicity/meta npm package versions 0.8.0 through 0.8.6 include code that references litter.catbox.moe, an anonymous and mutable file-hosting service. This host is known to be used in the TanStack/Shai-Hulud npm supply-chain compromise campaign as a second-stage payload delivery mechanism. The presence of such a host in runtime code is anomalous and indicative of malicious intent, as it allows the package to fetch and execute attacker-controlled code dynamically during installation or runtime. This behavior exposes users of the package to arbitrary code execution risks tied to the content served by the external host at the time of resolution.
Potential Impact
Consumers who install or load affected versions of @apicity/meta are exposed to arbitrary code execution risks because the package fetches and runs code from an untrusted, anonymous external host. This can lead to compromise of the user's environment, data theft, or further malware deployment. The threat is tied to the dynamic retrieval of attacker-controlled payloads, making the impact potentially severe depending on the payload served.
Mitigation Recommendations
No official patch or remediation guidance is currently available. Users should avoid installing or using affected versions of @apicity/meta (0.8.0 through 0.8.6). Consider removing the package from projects and replacing it with trusted alternatives. Monitor vendor advisories or the package repository for updates or official fixes. Due to the nature of the malicious code, manual code inspection and blocking network access to the referenced host may provide temporary mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13412
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cf8cbf8831d5391ae75a
Added to database: 08/06/2026, 18:16:44 UTC
Last enriched: 08/06/2026, 18:34:48 UTC
Last updated: 08/06/2026, 18:34:48 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.