Which versions of @applicationbuildingcenter/xcube-schema are malicious?

The following npm versions of @applicationbuildingcenter/xcube-schema are flagged malicious: 99.9.9, 99.9.12. Treat any of these as compromised.

How do I remediate @applicationbuildingcenter/xcube-schema if I installed it?

Remove @applicationbuildingcenter/xcube-schema from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @applicationbuildingcenter/xcube-schema — how do I know if it already compromised me?

If @applicationbuildingcenter/xcube-schema was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @applicationbuildingcenter/xcube-schema part of a known attack campaign?

Yes — @applicationbuildingcenter/xcube-schema is associated with the RLMA-2026-04667, RLUA-2026-05809 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @applicationbuildingcenter/xcube-schema across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @applicationbuildingcenter/xcube-schema (2 malicious versions).

Malicious package

@applicationbuildingcenter/xcube-schemanpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@applicationbuildingcenter/xcube-schema is a confirmed malicious npm package (MAL-2026-7037) that executes malicious code on install (malicious versions 99.9.9, 99.9.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @applicationbuildingcenter/xcube-schema (npm)

MAL-2026-7037

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @applicationbuildingcenter/xcube-schema

Malicious versions

2 flagged

99.9.999.9.12

Indicators of compromise (SHA-256)

085adce824751d295b38d77975e721c245889953bdac81aea58cf1f52e6628cf

d766464c3c4f5681a2ad6ca9086b6db401bb3230921a4b6ca7ee90cb410ff587

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @applicationbuildingcenter/xcube-schema (2 malicious versions).
If you installed it — respond
Remove @applicationbuildingcenter/xcube-schema from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @applicationbuildingcenter/xcube-schema was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @applicationbuildingcenter/xcube-schema on npm has been identified as a malicious package (versions 99.9.9, 99.9.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04667RLUA-2026-05809

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @applicationbuildingcenter/xcube-schema-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database