SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2302.07145 · AAAI · 2023

Practical Cross-System Shilling Attacks with Limited Access to Data

Ke Li, Hui Li, Liujuan Cao, Meifang Zeng, Bingchuan Jiang

arXiv · PDF · Open in the Atlas

Code that ran

1 of 1 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 1 has no contract verdict; 0 failures of our instrument; 0 no recorded run), measured 2026-11-22; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2302.07145.json · badge: /api/ran/2302.07145.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
KDEGroup/PC-Attack canonical (classifier label)
classifier basis not recorded on the link
1 ran · 0 no recorded run
FunctionStatusWhere it lives
test_moco Ran
ran on a synthesized input
KDEGroup/PC-Attack/generate.py
code served (permissive licence) · get_code("7b1762133d448bbd")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (5, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import torch.nn as nn

torch.manual_seed(0)

# Define minimal models that satisfy the function's usage
class SimpleGraphModel(nn.Module):
    def __init__(self, output_dim=4):
        super().__init__()
        self.linear = nn.Linear(5, output_dim)
    
    def forward(self, graph):
        # graph is expected to have a feature tensor
        return self.linear(graph.x)

class SimpleSeqModel(nn.Module):
    def __init__(self, output_dim=4):
        super().__init__()
        self.linear = nn.Linear(5, output_dim)
    
    def forward(self, graph):
        # Also processes graph.x
        return self.linear(graph.x)

# Define a minimal graph-like object
class SimpleGraph:
    def __init__(self, num_nodes=3, feature_dim=5):
        self.x = torch.randn(num_nodes, feature_dim)
    
    def to(self, device):
        self.x = self.x.to(device)
        return self

# Create the train_loader as a list of batches
# Each batch is a tuple of (graph_q, graph_k)
train_loader = [
    (SimpleGraph(num_nodes=3, feature_dim=5), SimpleGraph(num_nodes=3, feature_dim=5)),
    (SimpleGraph(num_nodes=2, feature_dim=5), SimpleGraph(num_nodes=2, feature_dim=5)),
]

# Create model instances
model_graph = SimpleGraphModel(output_dim=4)
model_seq = SimpleSeqModel(output_dim=4)

# Create options object with device attribute
class Options:
    def __init__(self):
        self.device = 'cpu'

opt = Options()

ARGS = {
    'train_loader': train_loader,
    'model_graph': model_graph,
    'model_seq': model_seq,
    'opt': opt,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (5, 4) — shape (5, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 1 samples lifted from this paper's linked repositories, 1 carry a function identity and 0 do not. Of the 1 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 1 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

In shilling attacks, an adversarial party injects a few fake user profiles into a Recommender System (RS) so that the target item can be promoted or demoted. Although much effort has been devoted to developing shilling attack methods, we find that existing approaches are still far from practical. In this paper, we analyze the properties a practical shilling attack method should have and propose a new concept of Crosssystem Attack. With the idea of Cross-system Attack, we design a Practical Cross-system Shilling Attack (PC-Attack) framework that requires little information about the victim RS model and the target RS data for conducting attacks. PC-Attack is trained to capture graph topology knowledge from public RS data in a self-supervised manner. Then, it is finetuned on a small portion of target data that is easy to access to construct fake profiles. Extensive experiments have demonstrated the superiority of PC-Attack over state-of-theart baselines. Our implementation of PC-Attack is available at https://github.com/KDEGroup/PC-Attack.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2302.07145")
get_code_for_paper("2302.07145")
have("2302.07145")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2302.07145.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2302.07145.svg)](https://syntology.ai/paper/2302.07145)

Connect an agent — have() is free.