Which versions of @outsmartly/metaobjects are malicious?

The following npm versions of @outsmartly/metaobjects are flagged malicious: 0.3.3-rc.1. Treat any of these as compromised.

How do I remediate @outsmartly/metaobjects if I installed it?

@outsmartly/metaobjects is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @outsmartly/metaobjects — how do I know if it already compromised me?

If @outsmartly/metaobjects was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @outsmartly/metaobjects part of a known attack campaign?

Yes — @outsmartly/metaobjects is associated with the IN-MAL-2026-010307 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 @outsmartly/metaobjects across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @outsmartly/metaobjects (version 0.3.3-rc.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @outsmartly/metaobjects across your stack and pipelines.

Malicious package

@outsmartly/metaobjectsnpm

@outsmartly/metaobjects is a confirmed malicious npm package (MAL-2026-10487) that steals credentials and exfiltrates sensitive data (malicious version 0.3.3-rc.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @outsmartly/metaobjects (npm)

MAL-2026-10487

Immediate action

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

npm uninstall @outsmartly/metaobjects

What this malware does

On import of the package main, dist/graphql-client.js constructs a singleton CustomGraphQLClient that takes the Shopify API URL built from the caller's METAOBJECTS_SHOPIFY_SHOP environment variable and unconditionally overwrites its host with the hardcoded value 'breadbox.edgefisher.com', preserving the original Shopify host only as an X-Forwarded-Host header. Every subsequent GraphQL request — including the caller's X-Shopify-Access-Token / X-Shopify-Storefront-Access-Token header sourced from METAOBJECTS_SHOPIFY_API_KEY, along with all query bodies and responses — is sent to that third-party domain instead of the configured Shopify endpoint. The destination is not Shopify, is not in the package's publisher namespace, is not documented in the README, and there is no opt-out or configuration override. The caller configures the package expecting their credentials to reach Shopify; the host rewrite silently diverts those credentials and the API traffic to an attacker/third-party-controlled host.

Malicious versions

1 flagged

0.3.3-rc.1

Indicators of compromise (SHA-256)

9ede306bb744e7248af8ac267412edc6cb95f6720dc3fd6f6766b7c3ce915853

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @outsmartly/metaobjects (version 0.3.3-rc.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @outsmartly/metaobjects across your stack and pipelines.
If you installed it — respond
@outsmartly/metaobjects is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @outsmartly/metaobjects was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @outsmartly/metaobjects before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @outsmartly/metaobjects on npm has been identified as a malicious package (version 0.3.3-rc.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010307

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @outsmartly/metaobjects-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database